Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by Lubodi-Code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_klines

Retrieve candlestick (kline) data for any trading symbol on Binance Spot. Specify interval from 1m to 1w and optional limit up to 1000 to analyze price trends.

Instructions

Velas (candlesticks) de un simbolo. interval: 1m,5m,15m,1h,4h,1d,1w, etc. limit: max 1000.

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>"
    },
    "name": "get_klines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
symbolYes
intervalNo1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The description discloses interval choices and a limit cap of 1000, but gives no information about the returned data structure, ordering, time ranges, or potential side effects. With no annotations, the description carries the full burden and falls short.

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

Conciseness4/5

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

The description is extremely brief and to the point, using two short sentences. The first sentence states the purpose, and the second lists constraints. It could be better structured, but it is concise.

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

Completeness2/5

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

With no output schema or annotations, the description needs to explain what a kline is and what the response contains. It only says 'velas' without defining OHLCV structure, ordering, or error handling, making it incomplete for an agent.

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?

The description adds meaning for interval (listing common values like 1m, 1h, 1d) and limit (max 1000), which are not explained in the schema. However, symbol is only implied and not elaborated, and defaults are not mentioned.

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

Purpose5/5

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

The description states 'Velas (candlesticks) de un simbolo' which clearly identifies the tool's purpose as retrieving candlestick data for a symbol. This distinguishes it from sibling tools like get_price (current price) and get_order_book.

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?

The description provides no guidance on when to use this tool versus alternatives. It lacks contextual clues about when klines are needed (e.g., historical analysis) or when to prefer other tools like get_price.

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