Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_asset_config

Retrieve asset details including fees, withdrawal limits, and network status, with deposit and withdrawal availability shown per network for Binance.US account configuration.

Instructions

Get details of all crypto assets including fees, withdrawal limits, and network status. Shows deposit/withdrawal enabled status per network.

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

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of the data returned (per-network enable flags, limits, fees), but says nothing about whether this is a public/unauthenticated endpoint, rate-limit behavior, or caching freshness — all of which matter 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 core verb and resource, with zero filler. The second sentence partially overlaps the first by restating network status as deposit/withdrawal enablement per network, which costs it a point.

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?

With no output schema, the description must convey what comes back, and it does so at a useful level of detail (fees, limits, network status, enable flags per network). For a one-optional-parameter read tool this is nearly sufficient; only auth/permission expectations are unaddressed.

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?

There is a single optional parameter (recvWindow) and schema description coverage is 100%, so the schema already documents it as a timing window capped at 60000. The description adds no further meaning about that parameter, which is the expected baseline when the schema does the work.

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 details of all crypto assets) and enumerates the content returned: fees, withdrawal limits, network status, and per-network deposit/withdrawal enablement. It does not differentiate itself from similar-looking siblings such as binance_us_cust_supported_assets or binance_us_staking_asset_info, so it stops short of a 5.

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 purpose implies when to reach for it (you need fee/limit/network metadata for assets), but there is no explicit when-to-use statement, no exclusions, and no named alternative. The agent must infer the routing decision from the noun phrase 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