Skip to main content
Glama
Sign In
MCP Pionex Management

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reduce futures grid position

pionex_bot_reduce_futures_grid
Destructive

Reduce position size of a Pionex futures grid bot order. Specify bot order ID, current price, and reduction amount to lower exposure on an existing strategy.

Instructions

Reduce futures grid position

Reduce position size of a futures grid order. 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>",
      "openPrice": "<openPrice>",
      "reduceNum": "<reduceNum>"
    },
    "name": "pionex_bot_reduce_futures_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
slippageNoReduction slippage
buOrderIdYesBot order ID
conditionNoTrigger reduction price (must be > 0)
openPriceYesCurrent price
reduceNumYesReduction amount: order precision * reduceNum
conditionDirectionNoTrigger direction: "1" (above current) or "-1" (below current)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The only added behavioral context is 'Weight: 1', a rate-limit detail, which is a small but genuine contribution. Nothing is said about reversibility or side effects on the grid strategy.

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?

Very short and front-loaded. The first line merely restates the title, which is mild redundancy, but there is no filler beyond that.

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

Completeness3/5

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

For a destructive trading mutation with six parameters and no output schema, the description covers the action but omits prerequisites, the relationship to its check variant, and what a successful reduction does to the running grid. Adequate but with clear gaps.

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%, so all six parameters (including the condition/conditionDirection trigger pair and the reduceNum precision multiplier) are documented in the schema itself. The description adds no param meaning beyond that, 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: 'Reduce position size of a futures grid order.' This is distinguishable from reduce_margin_futures_grid on the surface, but the description never mentions the near-identical _check sibling or any other grid tool, so differentiation is left to the name.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of pionex_bot_reduce_futures_grid_check, which the naming convention strongly implies is a required validation step. The agent must infer timing and ordering entirely.

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