Skip to main content
Glama
nirholas

Binance.US MCP Server

by nirholas

binance_us_cust_new_order

Place new trade orders on Binance.US using custodial solutions, supporting multiple order types including limit, market, stop-loss, and take-profit orders with optional ExpressTrade auto-funding.

Instructions

Place a new trade order through the custodial solution.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Supported order types:

  • LIMIT: Requires timeInForce, quantity, price

  • MARKET: Requires quantity OR quoteOrderQty

  • STOP_LOSS: Requires quantity, stopPrice (executes as MARKET when triggered)

  • STOP_LOSS_LIMIT: Requires timeInForce, quantity, price, stopPrice

  • TAKE_PROFIT: Requires quantity, stopPrice (executes as MARKET when triggered)

  • TAKE_PROFIT_LIMIT: Requires timeInForce, quantity, price, stopPrice

  • LIMIT_MAKER: Requires quantity, price (POST-ONLY order)

ExpressTrade Feature: When allowExpressTrade=true and custodial sub-account balance is insufficient, the full amount will be automatically transferred from the custodial partner.

Response includes: symbol, orderId, status, type, side, price, quantity, executedQty, and expressTradeFlag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolYesTrading pair (e.g., BTCUSD, ETHUSD)
sideYesOrder side: BUY or SELL
typeYesOrder type
timeInForceNoGTC (Good Til Canceled), IOC (Immediate or Cancel), FOK (Fill or Kill)
quantityNoOrder quantity in base asset
quoteOrderQtyNoOrder quantity in quote asset (MARKET orders only)
priceNoOrder price (required for LIMIT orders)
stopPriceNoStop/trigger price for stop orders
icebergQtyNoIceberg order quantity
assetNoAsset for ExpressTrade (the asset being sold)
allowExpressTradeNoEnable ExpressTrade for auto-funding
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: the requirement for a custodial API key, the ExpressTrade feature's auto-funding behavior, and the response structure. It also lists order types and their requirements, adding valuable context beyond basic functionality. A minor deduction because it doesn't mention potential risks, rate limits, or error conditions.

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 well-structured and front-loaded with the core purpose. Each section (warning, order types, ExpressTrade, response) adds essential information without redundancy. Sentences are direct and purposeful, making it easy to scan and understand quickly.

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?

Given the complexity (12 parameters, no annotations, no output schema), the description does a strong job. It covers purpose, prerequisites, order type specifics, a key feature (ExpressTrade), and response fields. However, it lacks details on error handling, rate limits, or examples, which would be helpful for a financial trading tool, preventing a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the baseline is 3. The description adds significant value by explaining parameter semantics for each order type (e.g., 'LIMIT: Requires timeInForce, quantity, price'), clarifying dependencies not obvious from the schema alone. It also details the ExpressTrade feature's impact on 'allowExpressTrade' and 'asset'. This compensates well, though it doesn't cover all 12 parameters individually.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Place a new trade order') and resource ('through the custodial solution'), distinguishing it from sibling tools like 'binance_us_new_order' (non-custodial) and 'binance_us_cust_cancel_order' (cancellation). The mention of 'custodial solution' provides precise differentiation.

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?

The description explicitly states when to use this tool ('Place a new trade order through the custodial solution') and includes a warning about prerequisites ('⚠️ REQUIRES CUSTODIAL SOLUTION API KEY'). However, it does not specify when NOT to use it or name alternative tools for non-custodial orders, which prevents a perfect score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nirholas/Binance-US-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server