Skip to main content
Glama
Sign In
MCP Pionex Management

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reduce margin of futures grid order

pionex_bot_reduce_margin_futures_grid
Destructive

Reduce margin on a Pionex futures grid bot order by transferring funds out, which lowers available margin and increases liquidation risk; validates amount before async execution.

Instructions

Reduce margin of futures grid order

Transfer margin out of a futures grid order. Runs the same validation as reduceMarginCheck (including the maxAmount check), then executes asynchronously. Directly reduces the order's available margin and raises liquidation risk — 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_reduce_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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructiveHint=true, readOnlyHint=false), yet the description adds substantive context: asynchronous execution, absence of a returned status field, the maxAmount validation, and raised liquidation risk. This is meaningful disclosure beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and resource, then layers constraints and warnings in short sentences. The "Weight: 1" line is extraneous but minor; nothing else is wasted.

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?

With no output schema, the description helpfully notes the missing status field, and annotations carry the safety profile, so an agent has enough to invoke it correctly. Only explicit usage/alternative routing is absent.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description only echoes the amount semantics via the maxAmount reference and adds no syntax or format detail, so the baseline 3 applies.

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 and resource ("Transfer margin out of a futures grid order") that clearly separates it from the sibling add_margin tool. It does not explicitly name siblings, but the operation is unambiguous.

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?

It implies the companion validation tool ("Runs the same validation as reduceMarginCheck") and warns "call with care," but gives no explicit when-to-use vs. when-not guidance or prerequisites. Usage must be inferred from the cautionary tone.

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