Retrieve a specific QuickBooks Online transfer by its unique ID to view details or verify transactions. Use this tool to fetch transfer records directly from QuickBooks for reporting or reconciliation.
Get a specific Transfer record by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| transferId | Yes | The unique Transfer ID |
Changes observed during successful MCP inspections.
v1.4.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('Get') with no side effects. However, it does not disclose failure modes (e.g., invalid ID) or any additional behaviors like rate limits or authorization requirements.
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 sentence with no unnecessary words. It is front-loaded with the core action and resource, making it easy for an agent to parse quickly.
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 simple get-by-ID operation, the description covers the essential purpose. It could mention that it returns the full transfer record or error handling, but given no output schema and low complexity, it is nearly complete.
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?
The input schema already fully describes the 'transferId' parameter as 'The unique Transfer ID'. The description adds minimal value by restating 'by its ID', which does not enhance understanding beyond the schema. Baseline of 3 is appropriate given 100% schema coverage.
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 action 'Get' and the resource 'a specific Transfer record', and specifies the identifier 'by its ID'. It effectively distinguishes this from sibling tools like qbo_transfers_list (returns a list) and qbo_transfers_create (creates a new one).
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_transfers_list or qbo_transfers_search. The description implies usage when you have a known transfer ID, but does not state when not to use it or mention alternative retrieval methods.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.