Skip to main content
Glama
Sign In
MCP Pionex Management

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Add margin to futures grid order

pionex_bot_add_margin_futures_grid
Destructive

Add margin to a futures grid order to adjust available balance and liquidation price. Transfers specified coin amount asynchronously.

Instructions

Add margin to futures grid order

Transfer margin into a futures grid order. Runs the same validation as addMarginCheck, then executes asynchronously. Directly affects available balance and the order's liquidation price — a funds operation, call with care. Does not return a status field (async processing). Weight: 1.

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": {
      "buOrderId": "<buOrderId>",
      "coin": "<coin>",
      "amount": "<amount>"
    },
    "name": "pionex_bot_add_margin_futures_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesTransfer currency
amountYesMargin amount to add / reduce (decimal)
buOrderIdYesBot order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds value beyond annotations by disclosing that it runs addMarginCheck validation, executes asynchronously, affects available balance and liquidation price, and omits a status field. The 'call with care' warning and async disclosure are genuinely useful. Annotations already cover destructive=true, so this layered context raises it above baseline.

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?

Front-loaded with the core action, then validation behavior, async nature, and side effects, ending with weight. All four lines earn their place with no padding.

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?

Covers the async execution, missing status field, validation flow, and balance/liquidation impact, which is thorough for a mutation without an output schema. Could go further on permissions or reversal, but it's substantially complete.

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 coverage is 100% and parameters are self-describing. The description adds no syntax, format, or constraint details about coin, amount, or buOrderId beyond what the schema already documents.

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 (add/transfer margin) and resource (futures grid order). Distinguishes itself from reduce_margin by naming 'add margin', but doesn't explicitly contrast with the sibling pionex_bot_reduce_margin_futures_grid or the _check variant.

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

Usage Guidelines3/5

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

Mentions it runs the same validation as addMarginCheck and executes asynchronously, implying a check-then-execute workflow. However, it never states when to use this vs the check variant or when not to call it.

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