Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_avg_price

Retrieve the current 5-minute rolling weighted average price for a Binance.US trading pair to support market analysis and pricing decisions.

Instructions

Get current 5-minute rolling weighted average price.

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": "binance_us_avg_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair symbol, e.g., BTCUSD

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 disclosure burden. It reveals the rolling-window behavior (5-minute weighted average), which is genuinely useful, but says nothing about authentication requirements, rate limits, whether the window is fixed or configurable, or what the response contains.

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, well matched to a simple read operation. It is arguably over-terse given the missing usage and return-format context, but nothing written 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 one-parameter read-only price tool with no output schema, the description is minimal but usable. It omits the return shape (whether the response includes the window size alongside the price) and whether the call is public or requires credentials, both of which an agent would want before invoking.

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?

Only one parameter, and the schema documents it fully at 100% coverage with a concrete example ('BTCUSD'). The description adds no symbol-format nuance (e.g., case sensitivity, separator conventions) beyond the schema, so the 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 specific verb ('Get') and a precise resource ('current 5-minute rolling weighted average price'), which is meaningfully different from a last-traded price tool. It does not name or contrast with any sibling such as binance_us_ticker_price, so differentiation is left to inference.

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 explicit when-to-use or when-not-to-use guidance, and no stated alternative for getting a spot/last price versus a rolling average. The agent must infer that this is the smoothed-price option rather than the latest-trade option.

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