Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_trade_volume

Retrieves the total trade volume for the past 30 days on Binance.US, calculated on a rolling daily basis at 00:00 UTC.

Instructions

Get total trade volume for the past 30 days. Volume is calculated on a rolling basis every day at 0:00 AM (UTC).

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

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits beyond structure — the 30-day window and the rolling recalculation at 0:00 AM UTC, i.e. data freshness — but omits whether the volume is account-scoped or market-wide, permission requirements, and response shape.

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, front-loaded with the outcome and followed by the one non-obvious behavior. No filler or redundancy.

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 simple read tool with one optional parameter and no output schema, the description covers what is measured and the time basis, but leaves the agent guessing about scope (own account vs. market) and the form of the returned value. A single scope clause would make it 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?

The single optional parameter recvWindow is fully described in the schema (100% coverage), so the schema already does the work. The description adds no additional meaning about recvWindow or about how the 30-day window interacts with it; 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 and resource ("Get total trade volume") plus a concrete time scope ("past 30 days"), which is enough to distinguish it from sibling tools such as binance_us_trade_fee or binance_us_cust_trade_history. It does not, however, explicitly name a sibling or state what it is not, so the differentiation is implicit.

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 30-day window implies the usage context but never says when to pick this over siblings or what its limits are. There is no explicit when-to-use, when-not-to-use, or named alternative.

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