Get detailed technical indicators (RSI, MACD, EMA, Bollinger Bands, etc.) for a crypto pair
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Trading pair (e.g. BTCUSDT) | BTCUSDT |
| interval | No | Candle interval | 1h |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation, but the description does not disclose potential side effects, authentication needs, rate limits, or response structure. For a simple getter, this is minimally acceptable but not fully transparent.
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 a single sentence, front-loaded with the action and resource. It contains zero filler words and conveys all necessary core information efficiently.
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 tool with only two parameters and full schema coverage, the description adequately conveys the primary purpose. However, there is no output schema, so the description could briefly mention the return format (e.g., a list of indicator values) to fully complete the picture. Still, it is sufficiently clear for typical usage.
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 input schema has 100% description coverage, with clear explanations for both parameters (symbol and interval). The description adds no extra meaning beyond the schema, merely echoing 'crypto pair' which duplicates the symbol field. Thus 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 uses a specific verb ('Get') and a precise resource ('detailed technical indicators') with concrete examples (RSI, MACD, EMA, Bollinger Bands). This clearly distinguishes it from sibling tools like get_crypto_signal (signals) and screen_crypto_market (market screening).
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 usage for obtaining raw indicator data, but it does not explicitly state when to choose this over the sibling tools or mention any exclusions. No alternatives are named in the description, leaving some ambiguity for an AI agent.
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 distinct purpose: get_crypto_indicators returns raw technical data, get_crypto_signal provides a single pair's trading signal, and screen_crypto_market scans multiple pairs. Although the last two both produce signals, the single-vs-batch distinction is clear.
All tool names follow a consistent pattern: [verb]_crypto_[noun] where verbs are 'get' or 'screen'. This makes the toolset predictable and easy to navigate.
Three tools is an appropriate, focused scope for a crypto signal server. Each tool serves a distinct core function without unnecessary bloat or duplication.
The set covers the primary workflow of retrieving indicators, getting a signal for one pair, and scanning the broader market. Minor gaps exist around historical data or configurable timeframes, but these are not critical to the server's stated purpose.