Get historical daily summaries for a specific asset.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of historical summaries (default: 7, max: 30) | |
| symbol | Yes | Asset symbol (e.g., BTC, ETH, SOL) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. Description adds the 'historical daily summaries' aspect, which is useful but not extensive. No contradiction.
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?
Single sentence, no wasted words. Could be slightly more structured but remains concise.
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?
Description is adequate for a simple tool with 2 parameters and strong annotations. However, it lacks details on the content of summaries (e.g., open/close/volume) or date range, given no output schema.
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% with descriptions for both 'limit' and 'symbol'. Description does not add additional meaning 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?
Description clearly states 'Get historical daily summaries for a specific asset,' specifying verb, resource, and scope. Distinguishes from siblings like 'get_asset_summary' (current) and 'get_price_history' (price-only).
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 explicit guidance on when to use this tool vs alternatives. Usage is implied by the description, but no when-not or comparative advice is provided.
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 has a clearly distinct purpose: asset details, summaries (current and historical), market cap, market summary, price history, surging/trending assets, and listing assets/market caps. No overlaps.
All tools follow a consistent verb_noun pattern with 'get_' for specific queries and 'list_' for enumerations. No mixing of conventions.
10 tools is well-scoped for a market data server, covering all essential read operations without being excessive or insufficient.
The set covers all common market data needs: asset details, summaries, market cap, price history, trending/surging assets, and full listings. No critical gaps for a read-only data server.
