get_market_overviewAggregated crypto futures market snapshot: total open interest (USD, with 1h/24h % change), total liquidations (24h), Fear & Greed index, average RSI across coins, plus a 30-day daily series of open interest and liquidations. Data aggregated across major exchanges.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral transparency. It discloses the data contents in detail, including time windows (1h/24h, 30-day series) and aggregation across major exchanges. It does not explicitly state read-only behavior or potential rate limits, but the detail provided is sufficient for a clear behavioral model.
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 two sentences with no redundant phrasing. It front-loads the core purpose ('Aggregated crypto futures market snapshot') and then lists the specific data points, earning every word.
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?
Despite having no output schema or annotations, the description fully specifies the tool's output by enumerating all key metrics and timeframes. For a zero-parameter read-only snapshot tool, this is complete and leaves no ambiguity for an agent.
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?
The tool has zero parameters, and the input schema contains no properties, meaning the description inherently covers the entire input space. The baseline for zero parameters is 4, and the description adds no irrelevant parameter details, so this score 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 identifies the tool as an aggregated crypto futures market snapshot, enumerating specific metrics such as open interest, liquidations, Fear & Greed index, and average RSI. This specificity distinguishes it from sibling tools like get_coin_summary or get_funding_rates, which are more narrowly focused.
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 implies use for a broad market-level overview rather than per-coin or per-exchange queries, providing clear context for when to use it. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.
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.