Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_allocations

Read-onlyIdempotent

Retrieve per-symbol Smart Order Routing (SOR) fills for a specific order, including price, quantity, and commission, with optional 24-hour time or order ID filtering.

Instructions

List Smart Order Routing (SOR) allocations — the per-symbol fills behind an SOR order.

Calls GET /api/v3/myAllocations (SIGNED, USER_DATA). IP weight 20 per call.

When to Use:

  • To see how an SOR order (binance_place_sor_order) was actually filled across symbols, with per-allocation price/qty/commission.

  • To page through allocations for a specific order via order_id.

When NOT to Use:

  • For regular (non-SOR) trade fills — use binance_get_my_trades.

Returns: A markdown list (or JSON) of allocations: allocationId, orderId/orderListId, symbol, side (isBuyer), qty/price/quoteQty (via fmt_num), commission + commissionAsset, maker/allocator flags, and time. Display is capped at MAX_DISPLAY_ROWS (50); JSON mode returns {count, truncated, displayLimit, items} rather than a bare array, so truncation stays valid JSON.

Windows: start_time/end_time (epoch ms or ISO-8601) accept a span of at most 24 h — enforced locally with a readable Error: before the call reaches Binance, since Binance would otherwise answer -1127.

Examples: params = {"symbol": "BTCUSDT"} params = {"symbol": "BTCUSDT", "start_time": "2024-01-01T00:00:00Z", "end_time": "2024-01-01T12:00:00Z"} params = {"symbol": "BTCUSDT", "order_id": 12345}

Error Handling: -1127 means the requested window is too wide (should not happen — the 24 h cap is enforced before the request). -1121 means an invalid symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral details: the IP weight (20 per call), the 24-hour window cap enforced locally with a readable error, the response format differences (markdown vs. JSON with truncation handling), and specific error codes (-1127, -1121). This goes well beyond annotations and prepares the agent for expected behavior.

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 with clear sections (purpose, when to use, returns, windows, examples, error handling) and every sentence contributes useful information. It is front-loaded with the core purpose and uses examples to clarify parameter usage, making it efficient despite its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all essential aspects: purpose, usage differentiation, behavior (IP weight, truncation, error handling), parameters (via examples and constraints), and output format. Given that an output schema exists, the description still adds critical context about local enforcement and display limits, making it fully complete for correct invocation.

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?

Although the schema itself provides descriptions for each parameter, the tool description enhances semantics with concrete examples (symbol, start_time/end_time, order_id), explains the 24-hour constraint, and clarifies the pagination cursor via `from_allocation_id`. It does not explicitly mention the `limit` parameter, but the schema covers it; the description still adds meaningful context beyond schema basics.

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 'List Smart Order Routing (SOR) allocations' — a specific verb and resource — and immediately distinguishes it from regular trade fills by naming the alternative `binance_get_my_trades`. This precise scoping leaves no ambiguity about what the tool does and how it differs from siblings.

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

Usage Guidelines5/5

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

The description includes explicit 'When to Use' and 'When NOT to Use' sections, directing agents to use this tool for SOR order fills and to use `binance_get_my_trades` for regular trades. It also mentions paging via `order_id`, providing clear guidance on invocation context.

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