Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_supported_assets

Retrieve asset eligibility and network details for a specified custodial rail, showing which assets support transfers and settlements. Requires a Custodial Solution API key.

Instructions

Get list of assets supported for custodial solution transfers and settlements.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Response includes:

  • transferEligible: Assets that can be transferred

  • settlementEligible: Assets that can be settled

Each asset entry contains:

  • asset: Asset symbol

  • precision: Decimal precision

  • network: Supported blockchain networks

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

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be 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, the description carries the full burden and does reasonably well: it flags the custodial-solution API key requirement upfront and describes the response structure (transferEligible, settlementEligible, per-asset fields). It does not state that the call is read-only, nor any rate limits or failure modes.

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?

The purpose sentence is front-loaded, the auth warning is visually separated, and the response fields are bulleted for fast scanning. The field-by-field breakdown is mildly verbose for a read-only lookup but each line still carries information.

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?

There is no output schema, so documenting transferEligible, settlementEligible, asset, precision, and network is genuinely valuable. Combined with the auth warning, the definition covers what an agent needs for this single-parameter read tool.

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 coverage is 100% and the schema already explains that rail is the uppercase custodial partner name, so the baseline is 3. The description adds nothing about the rail parameter itself, which is acceptable given 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?

A specific verb and resource: 'Get list of assets supported for custodial solution transfers and settlements.' It scopes the resource to the custodial rail, though it does not explicitly differentiate itself from the similarly named sibling binance_us_custodial_supported_assets.

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 implied by the custodial API key requirement and by the transfer/settlement framing, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for the non-custodial case.

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