List all pages of a Billy resource, returning compact or verbose details. Filter with supported parameters to retrieve specific records.
List every page of a Billy resource. Default response is compact and complete; verbose returns sanitized detail. Unknown filters are rejected.
| Name | Required | Description | Default |
|---|---|---|---|
| filters | No | ||
| verbose | No | ||
| resource | Yes |
Changes observed during successful MCP inspections.
v0.2.1Input schema / properties / resource / enumPrevious value: -[
- "accounts",
- "contacts",
- "invoices",
- "products",
- "bills",
- "bankPayments",
- "bankLines",
- "bankLineMatches",
- "bankLineSubjectAssociations",
- "daybooks",
- "daybookTransactions",
- "postings",
- "taxRates",
- "attachments",
- "files",
- "salesTaxReturns",
- "transactions"
-]New value: +[
+ "accounts",
+ "accountGroups",
+ "accountNatures",
+ "contacts",
+ "contactPersons",
+ "invoices",
+ "products",
+ "bills",
+ "bankPayments",
+ "bankLines",
+ "bankLineMatches",
+ "bankLineSubjectAssociations",
+ "daybooks",
+ "daybookTransactions",
+ "postings",
+ "taxRates",
+ "salesTaxRulesets",
+ "attachments",
+ "files",
+ "salesTaxReturns",
+ "transactions"
+]Input schema / properties / verboseAdded value: +{
+ "default": false,
+ "type": "boolean"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, non-destructive, idempotent behavior. The description adds valuable behavioral detail beyond those annotations: default responses are compact and complete, verbose returns sanitized detail, and unknown filters are rejected. This meaningfully helps an agent anticipate runtime behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, each carrying distinct information: the core operation, response behavior, and a validation constraint. No filler or redundancy, and the most important purpose is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a three-parameter list tool with no output schema, the description covers the essential usage aspects: resource choice, filters, verbose mode, and rejection of unknown filters. It stops short of detailing pagination mechanics or response shape, but the provided annotations for safety and idempotence reduce the need for further explanation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description partially compensates by explaining verbose behavior and filter validation. However, it does not explain how filters should be structured or which filter fields are supported, and resource semantics are left entirely to the schema enum.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action ('List every page') and a clear object ('a Billy resource'), making it obvious this is a paginated listing tool. It doesn't explicitly name sibling tools like billy_get, but 'every page' implies collection-wide listing rather than fetching a single item.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The wording implies use when an agent needs all pages of a Billy resource, along with optional filtering and verbose output. However, it does not explicitly contrast with alternatives such as billy_get or billy_period_overview, leaving the when-not-to-use guidance to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.