Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_supported_assets

Retrieve assets eligible for custodial transfers and settlements by rail, including asset symbols, precision, and supported networks. Use it to determine transfer-in and settlement-out eligibility.

Instructions

Get list of assets supported for custodial transfers and settlements.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Returns two lists:

  • transferEligible: Assets that can be transferred FROM custodial partner

  • settlementEligible: Assets that can be settled TO custodial partner

Each asset includes:

  • asset: Asset symbol

  • precision: Decimal precision

  • network: Supported networks for the asset

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rail": "<rail>"
    },
    "name": "binance_us_custodial_supported_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner identifier (all uppercase)

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

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses the authentication requirement up front and describes the shape and semantics of the return value (two lists plus per-asset fields), which the agent could not otherwise know since there is no output schema. It does not state rate limits or whether results are cached/live, which keeps it short of top marks.

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?

Front-loaded with the one-sentence purpose, then the auth warning, then a compact bulleted breakdown of the return value. Every line carries distinct information; the only mild redundancy is that the transferEligible/settlementEligible bullets are partly repeated by the per-asset field list.

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 single-parameter read-only lookup with no output schema, the description supplies the missing pieces: authentication requirement and full return structure (bucket names, field names, meanings). The remaining gap is the rail parameter's valid domain, which is left entirely to the schema.

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 required parameter, rail, and the description never mentions it — no explanation of what a custodial partner identifier is or which values are valid. Schema coverage is 100% and the schema already says "Custodial partner identifier (all uppercase)", so the baseline 3 applies rather than a penalty.

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 list of assets supported for custodial transfers and settlements") and goes further by defining the two returned buckets, transferEligible and settlementEligible. It does not differentiate itself from the near-identically named sibling binance_us_cust_supported_assets, leaving the agent to guess which of the two to call.

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 via the prerequisite warning ("REQUIRES CUSTODIAL SOLUTION API KEY") and the FROM/TO directionality of the two lists. There is no explicit statement of when to call this versus discovery/lookup siblings, and no exclusions.

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