Get a buy/sell/hold trading signal for a cryptocurrency pair with technical analysis
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Trading pair (e.g. BTCUSDT, ETHUSDT) | BTCUSDT |
| interval | No | Candle interval (1m,5m,15m,1h,4h,1d) | 1h |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'technical analysis' but does not explain the basis of the signal, potential limitations, real-time vs. delayed data, or any other behavioral traits. This is a significant gap for a trading signal 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?
The description is a single, clear sentence with no redundant or filler content. It efficiently communicates the core purpose without cluttering.
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?
While the tool is simple with only two well-documented parameters, the absence of annotations, output schema, and any behavioral context means the description leaves the agent without essential details like return format or how the signal is computed. It is minimally complete but lacks depth for reliable decision-making.
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%, so both parameters ('symbol' and 'interval') are already documented in the input schema. The description adds no additional meaning beyond what the schema provides, so the baseline score 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 the tool retrieves a buy/sell/hold trading signal for a cryptocurrency pair, which is a specific verb+resource. The term 'trading signal' differentiates it from sibling tools like get_crypto_indicators (which returns indicators) and screen_crypto_market (which screens markets).
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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or scenarios where the sibling tools would be more appropriate. The agent must infer usage solely from the tool name and sibling context.
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.