Loading ToolBench
Real-time crypto technical analysis signals API - RSI, MACD, EMA, Bollinger Bands, and actionable buy/sell signals
Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools have descriptions (10-20 chars above minimum), but descriptions lack actionable context for LLM selection. Parameter descriptions are minimal or missing (e.g., 'interval' lacks format/enum guidance). No documented output schemas. Error handling is generic ('Error: {message}'). Tool names follow verb_noun pattern correctly. No security issues detected (read-only operations, no secrets exposed).
Get detailed technical indicators (RSI, MACD, EMA, Bollinger Bands, etc.) for a crypto pair
Get a buy/sell/hold trading signal for a cryptocurrency pair with technical analysis
Scan top cryptocurrencies by volume and return trading signals for each
Parameter 'interval' lacks enum constraint and format guidance. Description says 'Candle interval' but does not specify valid values (1m,5m,15m,1h,4h,1d) as an enum. LLMs will hallucinate invalid intervals.
No documented output schema. Tool descriptions do not specify what fields the response contains (e.g., get_crypto_signal returns {symbol, interval, signal, indicators} but this is not documented). LLMs cannot plan downstream calls without knowing response structure.
Error handling is generic. Tool returns 'Error: {message}' with isError=true but provides no recovery guidance. If symbol is invalid or API fails, LLM has no hint to search for valid symbols or retry.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Parameter 'symbol' description includes example 'BTCUSDT' but does not specify format constraints (uppercase, length, valid exchange pairs). LLMs may pass lowercase or malformed symbols.
Tool description for 'screen_crypto_market' does not explain when to use it vs 'get_crypto_signal'. Both return signals; the distinction (single pair vs market scan) is not explicit. LLMs may pick the wrong tool.