Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_trade_fee

Retrieve current maker and taker spot trading fee rates by VIP level, optionally for a specific symbol or all symbols; BNB discounts are not included.

Instructions

Get your current maker & taker fee rates for spot trading based on your VIP level. BNB fee discount (25% off) is not factored in.

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

Input Schema

NameRequiredDescriptionDefault
symbolNoTrading pair symbol. If not specified, returns fees for all symbols.
recvWindowNoThe value cannot be greater than 60000

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

A3.8/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 full burden. It does add one genuinely valuable behavioral caveat — that the 25% BNB fee discount is not factored in — which prevents misinterpreting the returned rates. However, it omits whether the call requires signed/authenticated access, whether results are cached or real-time, and any rate-limit context.

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

Conciseness5/5

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

Two short sentences with zero filler; the core purpose is front-loaded and the BNB caveat follows immediately as a qualifier.

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

Completeness4/5

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

For a simple, zero-required-parameter read tool with a fully documented schema and no output schema, the description covers what is returned (maker and taker rates) and the key interpretation caveat. The remaining gap is the authentication/permission requirement, which an agent would want to know before calling.

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 both parameters (symbol, recvWindow) are already documented in the schema, establishing a baseline of 3. The description adds no further meaning about how symbol scoping interacts with fee lookup or what recvWindow affects here.

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?

States a specific verb ('Get') and resource ('maker & taker fee rates for spot trading'), plus the determining factor (VIP level). This is clearly distinct from siblings like binance_us_trade_volume or binance_us_account_info, which report volume and balances rather than fee schedules.

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?

Usage is only implied by 'Get your current...' — there is no explicit when-to-use statement, no guidance on when to pass a symbol versus omitting it (beyond the schema), and no mention of prerequisites such as API-key authentication for what is evidently a private account endpoint.

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