Binance MCP Server

调整逐仓保证金

trading_position_margin

Destructive

Adjust isolated position margin by increasing (type=1) or decreasing (type=2) the margin amount, and specify positionSide for hedge mode.

Instructions

调整逐仓保证金。type: 1=增加，2=减少（官方枚举）；amount 恒为正数。双向（Hedge）模式下须提供 positionSide。

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": {
      "symbol": "<symbol>",
      "amount": "<amount>",
      "type": "<type>"
    },
    "name": "trading_position_margin"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes
`amount`	Yes
`symbol`	Yes
`positionSide`	No

Output Schema

Name	Required	Description	Default
`type`	Yes
`amount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv3.0.1Aug 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / amount / description
```
Removed value: -"调整金额"
```

removedInput schema / properties / positionSide / description

Removed value: -"持仓方向（双向持仓模式时需指定）"

changedInput schema / properties / positionSide / enum

Previous value: -[
-  "BOTH",
-  "LONG",
-  "SHORT"
-]New value: +[
+  "LONG",
+  "SHORT"
+]

removedInput schema / properties / symbol / description
```
Removed value: -"交易对符号 如 BTCUSDT"
```

addedInput schema / properties / type / anyOf

Added value: +[
+  {
+    "const": 1,
+    "type": "number"
+  },
+  {
+    "const": 2,
+    "type": "number"
+  }
+]

removedInput schema / properties / type / description

Removed value: -"1=增加保证金 / 0=减少保证金"

removedInput schema / properties / type / enum
```
Removed value: -[
-  "0",
-  "1"
-]
```
removedInput schema / properties / type / type
```
Removed value: -"string"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "amount": {
+      "type": "number"
+    },
+    "type": {
+      "anyOf": [
+        {
+          "const": 1,
+          "type": "number"
+        },
+        {
+          "const": 2,
+          "type": "number"
+        }
+      ]
+    }
+  },
+  "required": [
+    "amount",
+    "type"
+  ],
+  "type": "object"
+}

Addedv2.0.3Jun 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark the tool as destructive (destructiveHint: true) and readOnly: false. The description adds behavioral context by specifying increase vs decrease with positive amounts, and by requiring positionSide in Hedge mode. It does not fully disclose risks such as liquidation impact, but it correctly reflects the mutating nature of the operation.

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 extremely compact—three short sentences, each conveying a distinct necessary fact: operation, enum semantics, and conditional requirement. No filler or redundant restatement of the name or schema.

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 tool with 4 parameters, moderate risk, and an output schema, this description is sufficient: it explains the enum, the amount constraint, and the Hedge-mode dependency. It does not list usage exceptions or deeper warnings, but the output schema covers return behavior, and the destructive hint already signals caution.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains type, amount, and positionSide usage. Symbol is not described, but its meaning is obvious and the description does add real clarity beyond the raw enum schema.

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?

Description clearly states the operation: adjusting position margin ('调整逐仓保证金') with type 1=增加 and 2=减少. The verb '调整' plus resource '逐仓保证金' is specific and distinguishes the tool from margin-type switching and leverage tools in the sibling list.

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 gives the essential usage condition for Hedge mode ('双向模式下须提供 positionSide') and clarifies the meaning of type values. It does not explicitly state when not to use the tool or point to alternatives, but the provided context is clear and actionable for normal usage.

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

Deploy Server