{"version":"2.1.283","anchor":"db-op-listquery-option-docs-now-state-limit-bounds-and-that","canonical_anchor":"db-op-listquery-option-docs-now-state-limit-bounds-and-that","heading":"Database tool instructions now explain limits and sorted queries","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/db-op-listquery-option-docs-now-state-limit-bounds-and-that","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Database tool instructions now explain limits and sorted queries\n\nClaude is now told that database result limits run from 1 to 1000, default 100, and that sorted queries return one page only\n\n**Unclear.** Which setting makes this database tool available is not known.\n\n**What**\n\nThe instructions Claude reads for its database tool now spell out how results come back:\n\n- `limit` can be from 1 to 1000, and is 100 if not given\n\n- a query with `order_by` returns a single page and never a `next_cursor`, the marker used to fetch the next page\n\n- to read a whole collection, Claude should either pass the `limit` it means or drop `order_by` and page through with `cursor`\n\nBefore, the instructions only said that `limit` and `cursor` page through a collection.\n\n**Why**\n\nWithout this, Claude could assume a sorted query can be paged and read only the first 100 results without noticing.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}