binance-mcp-enhanced
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BINANCE_TESTNET | No | Set to 'true' to enable testnet mode for paper trading. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Several tools have overlapping or confusingly similar purposes, such as the three trade-related tools (get_recent_trades, get_historical_trades, get_aggregate_trades) and the three ticker tools (get_24hr_ticker, get_trading_day_ticker, get_rolling_window_ticker). Without descriptions, agents could easily select the wrong one. get_avg_price and get_price also create ambiguity.
Most tools follow a get_ prefix, but then calculate_indicators, analyze_market, and compare_symbols break the pattern with bare verb forms. The convention is mostly consistent within the get_ group but mixed overall.
15 tools is at the upper boundary of well-scoped. The server covers a broad market data API with many similar endpoints, but each endpoint is distinct enough that the count is justifiable. Slightly heavy but not unreasonable.
The tool set covers a wide range of market data operations: order book, trades, klines, tickers, price, and even analysis. Missing common endpoints like exchangeInfo or server time, but the core market data surface is largely covered. The analysis tools add extra value.