Query QuickBooks Online customer records with filters and pagination to retrieve the account data you need for reporting or automation.
Query QuickBooks Online customers.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| where | No | SQL-style WHERE clause (e.g. Active = true) | |
| offset | No | ||
| sandbox | No | ||
| realm_id | Yes | QuickBooks company realm ID | |
| access_token | Yes | QuickBooks OAuth2 access token |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond 'Query,' such as pagination behavior, sandbox usage, authentication requirements, or what the response contains. It does not contradict the annotations, but it adds no useful transparency.
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?
The description is a single front-loaded sentence with no wasted words. It is concise, though its extreme brevity contributes to under-specification elsewhere rather than being verbose.
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 six-parameter tool requiring OAuth credentials and offering filtering, pagination, and sandbox options, the description is incomplete. It does not explain the query capabilities, return format, or how the parameters should be used, leaving the agent with little operational context beyond the tool name.
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?
Schema description coverage is exactly 50%, with limit, offset, and sandbox left undocumented in the schema. The description does not compensate by explaining pagination, the WHERE clause, sandbox behavior, or how the required access token and realm ID are used. It provides no meaning beyond the schema itself.
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 specific verb and resource: querying QuickBooks Online customers. It distinguishes the tool from sibling resources like quickbooks_items, quickbooks_payments, and quickbooks_invoices by naming the specific resource. However, 'Query' is somewhat generic and does not clarify whether this is a list, search, or filtered retrieval operation.
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 description offers no guidance on when to use this tool versus alternatives. It does not mention filtering, pagination, or when a more specific QuickBooks tool such as quickbooks_invoices or quickbooks_payments should be selected instead. The implied usage is simply 'query customers,' which is minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.