The unanimous club — tokens listed on ALL monitored exchanges (the strongest listing consensus signal). Returns the full club list with grades. Pass an optional symbol to check membership for one base ticker.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | No | Optional base ticker to check membership (e.g. BTC) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description indicates read-only behavior (returns lists) but does not disclose any additional behavioral traits like potential rate limits or data freshness.
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 well-structured sentences. First defines the tool's concept, second explains output and optional parameter. No redundant information.
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 no output schema, the description sufficiently explains return of full club list with grades and optional membership check. No critical missing context for this straightforward tool.
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 has 100% coverage for the single parameter. Description adds value by explaining that the symbol checks membership for one base ticker, enhancing understanding 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 clearly states the tool returns tokens listed on all monitored exchanges (the strongest listing consensus signal) with grades. It distinguishes itself as the 'unanimous' club among siblings like get_microburst, but does not explicitly contrast use cases.
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 mentions optional symbol parameter for membership check, implying use for consensus signals. No explicit guidance on when not to use or alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.