MCP server for Binance Testnet read-only tools
All 7 tools have clear verb-noun naming (getSpotPrice, getKlines, etc.) and descriptions present. However, descriptions are minimal (10-50 chars), falling below the 50-200 char baseline for LLM-optimized docs. Input schemas are visible and typed, but lack depth: most parameters have only basic type+description, no enums for constrained values (e.g., interval should be enum: 1m|5m|1h|4h|1d), no min/max bounds on numeric params (limit, symbol validation). Output schemas are not documented, LLMs cannot plan downstream calls or extract structured data. Error handling is absent from visible code. All tools are READ_ONLY (safe), but descriptions don't state this explicitly. Parameter descriptions are generic ('Trading pair symbol') without format guidance or examples of valid values.
Get account balances and asset holdings
Get candlestick data (OHLCV) for a trading pair
Get list of open orders for the account
Get the order book (bid/ask levels) for a trading pair
Get the current spot price for a trading pair
Get trading rules and constraints for a symbol
Get historical trades for the account
Output schemas not documented. LLMs cannot infer what fields are returned or plan downstream tool calls. No response structure visible in code.
Descriptions are 10-50 characters, well below 50-200 char baseline. Too terse to guide LLM selection. E.g., 'Get the current spot price for a trading pair' lacks WHEN to use, prerequisites, or return structure.
Constrained parameters lack enums. 'interval' in getKlines accepts free-form strings instead of enum [1m, 5m, 1h, 4h, 1d]. LLMs will hallucinate invalid intervals.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | <=2025-11-25 | v2 |
Numeric parameters lack bounds. 'limit' in getKlines has no min/max (spec says max 1500, default 100). LLMs may pass absurd values.
No error handling guidance visible. If a symbol is invalid or API fails, LLMs have no recovery path. No actionable error messages documented.