Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_exchange_info

Fetch Binance.US exchange trading rules and trading pair details, optionally filtered by symbol(s) or permissions, to validate markets and trading access.

Instructions

Get current exchange trading rules and trading pair information from Binance.US. Can filter by specific symbol(s) or permissions.

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

Input Schema

NameRequiredDescriptionDefault
symbolNoSingle trading pair symbol to filter (e.g., BTCUSD). Cannot be used with 'symbols' parameter.
symbolsNoArray of trading pair symbols to filter (e.g., ['BTCUSD', 'ETHUSD']). Cannot be used with 'symbol' parameter.
permissionsNoFilter by trading permissions. Default is ['SPOT'].

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

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'Get' plus 'current' implies a non-destructive read of live data, which is useful. However, it says nothing about authentication requirements, rate-limit weight, or that the unfiltered response can be a very large payload — meaningful omissions for a market-data endpoint.

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?

Two short sentences, front-loaded with the resource and followed by the filtering capability. No filler or repetition. It is terse rather than padded, though it could have used the second sentence for a more useful detail than restating filters.

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?

With no annotations and no output schema, the description must establish safety and return shape on its own. It conveys the conceptual content (trading rules and pair info) but not the response structure, and there is no output schema to compensate. Adequate for a read-only reference endpoint, but thin given the absence of supporting metadata.

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 all three parameters (symbol, symbols, permissions) are documented in the schema, including the mutual exclusivity of symbol/symbols and the default of ['SPOT']. The description restates the filtering surface but adds no syntax, format, or edge-case detail beyond the schema, so 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?

Names a specific verb and resource: 'Get current exchange trading rules and trading pair information.' An agent can immediately tell this is a reference/metadata lookup rather than an order or account operation, which separates it from most siblings. It stops short of explicitly naming which sibling to use instead for related lookups.

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

Usage Guidelines3/5

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

The sentence 'Can filter by specific symbol(s) or permissions' implies how to narrow the call, and the resource type implies when to reach for it (symbol/rule discovery before trading). There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named.

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