get_dealFetch a cp0x deal by slug to view its description, races, and referral-code links when full details are needed.
Get a cp0x deal with its description and races. Use this when a deal slug is known and its full details are needed; links include a cp0x referral code.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Deal slug from the cp0x catalog. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds useful return context by noting that the response includes the deal description, races, and links containing a cp0x referral code.
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 sentences, front-loaded with the core action and followed by precise usage guidance. Every clause adds relevant information without repetition.
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 single-parameter read tool with rich annotations and full schema coverage, the description is nearly complete. It covers purpose, usage, and partial return content, though it does not fully describe the response shape or failure behavior.
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%, so the slug parameter is already fully documented. The description only restates that the slug must be known, adding no extra format or syntax guidance beyond the schema.
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 states a specific verb and resource: retrieve a cp0x deal with its description and races. It does not explicitly name the sibling list_deals as the discovery alternative, so sibling differentiation is implied rather than stated.
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?
It clearly states when to use the tool: when a deal slug is known and full details are needed. This implicitly separates it from list_deals, but it does not explicitly name alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.