Get detailed purchase data from QuickBooks Online by purchase ID, including line items and vendor info. Use it to audit expenses and verify transactions.
Get detailed information about a specific purchase by its ID. Returns full purchase details including line items and vendor info.
| Name | Required | Description | Default |
|---|---|---|---|
| purchaseId | Yes | The unique purchase ID |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description should disclose behavioral traits. It only describes the basic function and return, but fails to mention that this is a read-only operation, what happens on missing ID, or any rate limits.
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?
Two concise sentences that front-load the purpose and specify return details. No unnecessary words.
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?
Given the simple parameter set (1 param, no output schema), the description covers the purpose and return. It could mention error handling or permissions, but it's sufficient for a basic get tool.
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 coverage is 100% with a clear description for 'purchaseId'. The tool description adds minimal value ('by its ID'), so baseline 3 is appropriate.
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 clearly states the verb 'Get', the resource 'purchase', and what is returned ('full purchase details including line items and vendor info'). It distinguishes from sibling list tools like qbo_expenses_list_purchases.
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?
No explicit guidance on when to use this tool versus alternatives like qbo_expenses_get_bill. The description implies usage when a purchase ID is known, but does not provide when-not or alternative scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.