get_coin_summaryFull derivatives snapshot for one coin: price and market cap, open interest with 1h/4h/12h/24h change, volume, liquidations (total/long/short), long/short ratio per exchange, and current funding rate per exchange (OI-weighted aggregate included). The single best tool for “what's happening with X futures”.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Coin ticker, e.g. BTC |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosure. It thoroughly lists what data is returned and even notes the OI-weighted aggregate for funding rates. It does not cover potential edge cases like rate limits or response structure, but the level of detail is strong for a snapshot tool.
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 concise sentences. The first sentence lists the content in a clear, front-loaded format; the second provides a memorable usage recommendation. No wasted words.
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?
The description enumerates all major return components, which is important since there is no output schema. However, it could benefit from clarifying the structure (e.g., per-exchange values vs. aggregate), but the information provided is sufficiently complete for a summary 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 coverage is 100% for the single 'symbol' parameter, which is already described as 'Coin ticker, e.g. BTC'. The description adds no additional parameter semantics (e.g., case sensitivity, whether to include the 'USDT' suffix), but given the high schema coverage, the baseline of 3 is 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?
The description clearly states it provides a 'Full derivatives snapshot for one coin' and enumerates the exact metrics included (price, open interest, volume, liquidations, long/short ratio, funding rate). This distinguishes it from sibling tools that focus on narrower aspects like funding rates or exchange breakdowns.
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?
The description explicitly claims it is 'The single best tool for “what's happening with X futures”', which gives clear context for when to use it. However, it does not explicitly mention alternative tools or conditions when a different tool might be more appropriate.
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.
Each tool targets a distinct data surface: list markets, single-coin summary, exchange breakdown, funding rates, market overview, price history, and exchange list. Even where data overlaps, the descriptions clearly delineate scope (e.g., get_coin_summary vs. get_funding_rates).
All tool names follow a consistent verb_noun pattern (get_* and one list_*), using clear, memorable resource nouns. No mixing of camelCase or inconsistent verb styles.
Seven tools is well-scoped for a crypto derivatives data API, providing enough granularity without bloat. Each tool earns its place and the count sits comfortably within the ideal range.
The surface covers current snapshots, historical time series, per-exchange breakdowns, funding details, market aggregates, and exchange metadata. No obvious dead ends or missing operations for the stated purpose.