Retrieve a single expense claim with its trip, line items, and employee details to review or audit business-travel reimbursements.
Get one claim with its trip, items and employee details.
| Name | Required | Description | Default |
|---|---|---|---|
| claim_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It does usefully reveal that the response is an expanded record (trip, items, employee), but says nothing about permissions, error behavior for missing/inaccessible claims, or response size.
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?
A single front-loaded sentence with zero filler; the payload contents are appended efficiently.
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?
A simple one-parameter read with no output schema, and the description compensates by naming the returned sub-resources. Only the claim_id format and failure behavior are missing, which is minor for this tool shape.
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?
Only one parameter and schema description coverage is 0%, so the schema adds no semantics for claim_id. The description confirms the parameter identifies a claim but gives no format, source, or example beyond that.
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?
States a specific verb and resource ('Get one claim') and clarifies the payload includes trip, items and employee details. 'One claim' implicitly separates it from the sibling list_claims, but no sibling is named explicitly.
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?
Usage is only implied: the single required claim_id signals a lookup by identifier. The description never says when to prefer this over list_claims or check_claim, nor what happens if the claim_id is unknown.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.