Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_undo_transfer

Reverses a custodian transfer that hasn't been fully processed, returning the asset and amount via the custodial partner using the original transfer ID.

Instructions

Undo a previous transfer from your custodial partner.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Use this to reverse a custodian transfer that hasn't been fully processed.

Response includes:

  • transferId: New transfer ID for the undo operation

  • asset: Asset being returned

  • amount: Amount being returned

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

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
originTransferIdYesOriginal transfer ID 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
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 meaningful work: it flags the custodial solution API key requirement and states the state precondition (transfer not fully processed). It does not explain failure behavior if the transfer is already processed, or whether the undo is itself reversible.

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-loads the action, then the key warning, then the return fields as a short bullet list. Every element earns its place; the response list is justified because no output schema exists.

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?

Covers the prerequisites, eligibility condition, and return values, which is largely sufficient for a two-parameter tool. It omits what happens on failure (e.g. transfer already settled) and any rate-limit or timing constraints, which matter for an irreversible-looking reversal call with no annotations to fall back on.

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%, with rail (uppercase partner name) and originTransferId fully documented in the schema. The description adds no syntax, format, or constraint detail beyond that, so the 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 ("Undo a previous transfer from your custodial partner") that clearly separates it from the history and balance siblings. It does not differentiate from the near-identically named sibling binance_us_custodial_undo_transfer, leaving potential ambiguity between the two.

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?

Gives an explicit eligibility condition: use it to reverse a custodian transfer that hasn't been fully processed. That is real guidance about when the tool applies, though it offers no when-not cases or named alternatives for transfers that already settled.

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