Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_ticker_price

Fetch current prices for one or multiple cryptocurrency symbols on Binance.US to track market values.

Instructions

Get latest price for symbol(s).

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_ticker_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoSymbol (e.g., BTCUSD). Cannot use with 'symbols'.
symbolsNoArray of symbols. Cannot use with 'symbol'.

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, and it discloses almost nothing: no rate-limit/weight information, no statement about whether symbols are case-sensitive, no indication of what a missing or invalid symbol yields. Only the word 'Get' weakly signals a read-only operation.

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?

One short sentence, front-loaded with the verb and resource, with no filler. It is economically written, though the brevity edges toward under-specification rather than optimal concision.

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?

This is a simple two-parameter, zero-required read tool with no output schema, so the bar is low, but the description still leaves the agent guessing about return shape (price only vs. a ticker object) and about exchange-level constraints. It is minimally viable rather than complete.

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 the schema itself states the mutual exclusion between 'symbol' and 'symbols', so the parameter contract is already documented. The description's 'symbol(s)' adds only a hint that both single and batch forms exist, which is the baseline level of value.

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?

The description names a specific verb and resource — 'Get latest price' — so the agent knows this is a spot quote lookup. It does not differentiate itself from siblings like binance_us_avg_price, binance_us_ticker_24hr, or binance_us_ticker_book, which return related but distinct 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 guidance on when to use this versus the 24hr ticker, book ticker, or average price tools, nor any note about the single-symbol versus multi-symbol modes. The agent must infer the distinction from tool names alone.

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