Fetch real-time cryptocurrency prices and 24-hour market data for multiple coins. Returns current price in USD, 24h price change percentage, market cap, and trading volume. Use for crypto portfolio tracking, price alerts, or comparing digital assets.
| Name | Required | Description | Default |
|---|---|---|---|
| coins | No | List of cryptocurrency symbols or names to fetch price data |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already signal a safe read operation. The description adds meaningful context by disclosing the output includes current price in USD, 24h price change, market cap, and volume, which is useful since no output schema exists. It does not contradict annotations.
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, front-loads the main action and return values, then gives concise usage guidance. Every sentence adds value with no wasted words or redundancy.
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?
For a simple one-parameter read-only tool with no output schema, the description covers purpose, data returned, and use cases. It also implicitly differentiates from sibling tools by focusing on crypto, making it sufficiently complete for an agent to select and invoke correctly.
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 100% per context signals, and the coins parameter is already well-documented in the schema with examples. The description's mention of 'multiple coins' slightly reinforces the array semantics but adds no extra detail beyond the schema, so baseline 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 the tool fetches real-time cryptocurrency prices and 24-hour market data for multiple coins, listing specific return fields (USD price, 24h change, market cap, volume). This specific verb+resource combination distinguishes it from sibling tools like get_stock_data and get_exchange_rates.
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?
It provides explicit use cases: 'Use for crypto portfolio tracking, price alerts, or comparing digital assets.' While it doesn't explicitly mention when not to use it or name alternatives, the context makes it clear this is for crypto only, which differentiates it from non-crypto sibling tools.
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.
The tools are mostly distinct, but get_crypto_prices and track_crypto_portfolio both deal with cryptocurrency data, which could cause confusion. However, the descriptions clarify that one is for general price lookup and the other for portfolio tracking, so the overlap is manageable.
All tool names follow a consistent verb_noun pattern in snake_case: get_crypto_prices, get_exchange_rates, get_stock_data, screen_stocks, track_crypto_portfolio. There is no mixing of naming conventions.
With 5 tools, the server is well-scoped, covering crypto, forex, stocks, and screening without unnecessary bloat. The count is appropriate for the domain.
The server covers the main market data needs for crypto, forex, and equities, plus stock screening. Missing historical data or stock portfolio tracking are minor gaps that agents can work around.