Fetch a specific deposit record using its unique ID to access deposit details for verification or financial reporting.
Get a specific Deposit record by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| depositId | Yes | The unique Deposit 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. The description describes a read operation ('get'), which is straightforward. It does not add additional behavioral details such as error handling or response format, but the risk is minimal.
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?
Single sentence, directly to the point, with 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?
With no output schema, the description does not mention the response structure. For a simple get operation, the context is adequate but could be improved by noting expected return fields.
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 100% for the single parameter. The description adds 'by its ID' which aligns with the schema but does not provide additional semantic context beyond what the schema already states.
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?
Description clearly states the action (Get) and resource (Deposit record) with the method (by ID). It distinguishes from sibling tools like qbo_deposits_list and qbo_deposits_create.
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?
Description implies usage context: when you have a specific ID. However, it does not explicitly state when not to use it or suggest alternatives (e.g., use list for multiple records).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.