Get current market quotes for cryptocurrency spot pairs to track real-time trading prices and liquidity across decentralized exchanges.
Returns the latest market quote for 1 or more spot pairs.
| Name | Required | Description | Default |
|---|---|---|---|
| contract_address | No | ||
| network_id | No | ||
| network_slug | No | ||
| aux | No | ||
| convert_id | No | ||
| skip_invalid | No | ||
| reverse_order | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only states the purpose. It fails to disclose behavioral traits like read-only nature, authentication needs, or rate limits.
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 9-word sentence, which is concise but under-specified given the tool's complexity. It is not overly verbose but lacks necessary detail.
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?
Given the 7 parameters and no output schema or annotations, the description is incomplete. It does not explain input usage, return format, or distinguish from siblings.
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 0%, and the description does not explain any of the 7 parameters. Parameter names (e.g., contract_address, network_id) are insufficient for proper usage.
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 it returns the latest market quote for spot pairs, using a specific verb and resource. It does not explicitly differentiate from sibling tools like dexPairsOhlcvLatest, but the function is distinct enough.
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 guidance is provided on when to use this tool versus alternatives, such as cryptoQuotesLatest or other dex tools. No prerequisites or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.