Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_prevented_matches

Read-onlyIdempotent

List orders rejected by Self-Trade Prevention (STP) for a symbol, showing blocked price and quantity. Query by prevented match ID or order ID to audit STP behavior.

Instructions

List orders rejected by Self-Trade Prevention (STP) for a symbol.

Calls GET /api/v3/myPreventedMatches (SIGNED, USER_DATA). IP weight 2 when queried by prevented_match_id, 20 when queried by order_id.

When to Use:

  • To see which of your own orders were prevented from matching against each other (STP), including the price and quantity that was blocked.

  • To audit STP behavior for a specific order via order_id.

When NOT to Use:

  • For orders that DID execute — use binance_get_my_trades (trade history).

Returns: A markdown list (or JSON) of prevented matches: preventedMatchId, tradeGroupId, taker/maker order ids, maker symbol, price, maker quantity prevented (via fmt_num), the self-trade-prevention mode, and the transaction 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.

Pagination: Only valid together with order_id: from_prevented_match_id is an inclusive cursor — pass the last-seen preventedMatchId (or one past it) to page forward, and limit (only sent when from_prevented_match_id is set; Binance default 500, max 1000) caps how many rows come back per call. Display is additionally capped at MAX_DISPLAY_ROWS (50) regardless of limit.

Examples: params = {"symbol": "BTCUSDT", "prevented_match_id": 1} params = {"symbol": "BTCUSDT", "order_id": 12345, "from_prevented_match_id": 5}

Error Handling: Exactly one of prevented_match_id or order_id is required — validated locally before the call. from_prevented_match_id requires order_id. -1121 means an invalid symbol; -2013/-2011 mean the order id does not exist.

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

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds IP weight details, local validation rules, error code meanings, display caps, and the JSON response structure. This provides rich behavioral context that annotations alone do not cover, and nothing contradicts the annotations.

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 headers, bullet points, and examples. Every section adds value, and the content is front-loaded with the purpose before diving into details. There is no fluff or redundancy.

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 necessary aspects: purpose, usage, pagination, examples, error handling, and return format. It also notes the output schema behavior for JSON mode. Given the tool's complexity, nothing is missing for an agent to call it correctly.

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

Parameters5/5

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

The description explains parameter relationships (mutual exclusivity of prevented_match_id and order_id, from_prevented_match_id requiring order_id, limit only sent with from_prevented_match_id) and adds context like display caps. This goes well beyond the schema's individual parameter descriptions, giving the agent a full understanding of how to combine parameters correctly.

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 opens with a specific verb and resource: 'List orders rejected by Self-Trade Prevention (STP) for a symbol.' It also names the alternative tool (binance_get_my_trades) in the 'When NOT to Use' section, clearly distinguishing this tool 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 has explicit 'When to Use' and 'When NOT to Use' sections, including a direct reference to an alternative tool for executed trades. It also provides detailed pagination conditions, making the decision to use this tool unambiguous.

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