Retrieve detailed contract data by UUID, including escrow status, terms, and involved parties for BotDigit marketplace projects.
Get detailed contract data including escrow status, terms, and parties.
| Name | Required | Description | Default |
|---|---|---|---|
| contract_id | Yes | UUID of the contract |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Get' implies a read operation and it discloses what data is returned (escrow status, terms, parties), but it says nothing about permissions, error behavior for an invalid contract_id, or response shape.
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 waste that states the resource and the salient returned fields. It is appropriately sized, though minimal.
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 one-parameter read tool with full schema coverage and no output schema, the description adequately signals the returned content. Only minor gaps remain around failure modes and auth requirements.
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 single well-documented contract_id (UUID), so the schema already supplies parameter meaning. The description adds no syntax or format detail beyond it, making the baseline 3 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?
States a specific verb (Get) and resource (contract) and enumerates the returned content (escrow status, terms, parties). It implicitly distinguishes itself from sibling list_contracts via 'detailed', but does not name the alternative 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 implied rather than stated: an agent can infer this fetches a single contract by id versus the list tools. There is no explicit when-to-use/when-not guidance or prerequisite mention.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.