Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_rolling_window

Fetch rolling-window price change statistics for one or more Binance.US symbols, using custom windows from 1 minute to 7 days.

Instructions

Get rolling window price change statistics with custom window sizes (1m to 7d).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "binance_us_rolling_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFULL (default) or MINI.
symbolNoSymbol (required if 'symbols' not provided).
symbolsNoArray of symbols (required if 'symbol' not provided).
windowSizeNoWindow size. Default 1d. Options: 1m, 2m, 3m, 4m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 7d

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.9/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 implies read-only market data but says nothing about authentication requirements, rate limits, pagination, or what happens when neither symbol nor symbols is given. The one behavioral detail it adds is the supported window range, which the schema already enumerates.

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?

A single front-loaded sentence with no filler, and the key capability comes first. The '(1m to 7d)' parenthetical is mildly redundant with the windowSize enum, but it is short and orients the reader quickly.

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 four-parameter market-data endpoint with no annotations and no output schema, the description is minimally adequate: the schema covers every parameter, but the definition leaves the agent to infer that this is an unauthenticated read and how the mutually exclusive symbol/symbols pair behaves. It is sufficient to call correctly but not to choose confidently among siblings.

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% and both enums (type, windowSize) are documented inline, so the schema already does the heavy lifting. The description only restates the window-size range from the enum and adds no meaning about symbol vs symbols exclusivity or the FULL/MINI difference beyond what the schema says. Baseline 3 applies.

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 concrete verb and resource: 'Get rolling window price change statistics', plus the customizable scope of window sizes. An agent immediately knows this returns price-change metrics over an adjustable window. It does not differentiate from sibling market-data tools such as avg_price or the 24h ticker, so it stops short of a 5.

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 statement that this is a public market-data read, and no routing to or away from alternatives. The only implied usage is that the caller wants rolling-window change stats, which the name already conveys.

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