Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_undo_transfer

Reverse a custodial partner transfer by its transfer ID and rail. Use it to undo eligible prior custodian transfers when a transfer must be corrected.

Instructions

Undo a previous transfer from your custodial partner.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY ⚠️ Only certain transfers can be undone - check with your custodial partner.

This reverses a previous custodian transfer by its transfer ID.

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>",
      "originTransferId": "<originTransferId>"
    },
    "name": "binance_us_custodial_undo_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner identifier (all uppercase)
originTransferIdYesThe transfer ID of the original transfer to undo

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?

With no annotations, the description carries the full behavioral burden. It usefully discloses the API-key requirement and eligibility caveat, but it does not explain mutation consequences, idempotency, error behavior, or what a successful undo returns.

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?

The description is short and front-loaded: it states the action first, then highlights the two operational warnings. Every sentence adds useful information with no wasted wording.

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 two-parameter mutation tool with no annotations or output schema, the description covers the essential context: purpose, authentication, eligibility, and the identifying parameter. Minor gaps remain around return behavior and how to check whether a transfer is undoable.

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 are already documented. The description adds only that the operation uses a transfer ID; it does not add meaning beyond the schema for the rail parameter or the transfer ID format.

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?

The description clearly states a specific verb and resource: undoing a previous custodial transfer by transfer ID. It is understandable without opening the schema, though it does not explicitly differentiate itself from the similarly named sibling binance_us_cust_undo_transfer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It indicates when to use the tool (to reverse a previous transfer) and gives two important conditions: a custodial solution API key is required and only certain transfers can be undone. It does not name alternatives or explain how to determine which transfers are eligible.

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