Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_klines

Retrieve OHLCV candlestick data for a Binance.US trading pair at a chosen interval, with optional time range and limit, to analyze price movement and build charts.

Instructions

Get Kline/candlestick data for a trading pair. Returns OHLCV data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "interval": "<interval>"
    },
    "name": "binance_us_klines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of klines. Default 500, max 1000.
symbolYesTrading pair symbol, e.g., BTCUSD
endTimeNoEnd time in ms
intervalYesKline interval: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M
startTimeNoStart time in ms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / endTime / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / startTime / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It notes the return payload is OHLCV, which is helpful, but omits that this is a public unauthenticated endpoint, that request weight/rate limits scale with the limit parameter, and how startTime/endTime interact with limit-based pagination. For a market-data endpoint with zero annotation coverage, these omissions are significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the verb and resource, with no redundant or filler wording. Nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter read-only market-data tool with full schema coverage and no output schema, the definition is minimally sufficient. It still leaves out behavior an agent would want, chiefly rate-limit/weight implications of large limit values and the time-window semantics of startTime/endTime.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including the interval enum, limit bounds, and millisecond timestamps is already documented. The description adds nothing about parameter interaction (e.g., that startTime/endTime narrow the window and limit caps rows). Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Get Kline/candlestick data for a trading pair', with the return shape ('OHLCV data') clarified. An agent can tell this is a market-data retrieval tool. However, it does not distinguish itself from nearby siblings such as binance_us_agg_trades or binance_us_avg_price, which also return price data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when to prefer agg_trades or avg_price over klines, and no statement of prerequisites. The agent must infer usage purely from the resource name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools