Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics

New order

pionex_orders_new_order
Destructive

Place buy or sell orders on Pionex by specifying symbol, side, and order type. Supports limit and market orders with price, size, or amount parameters.

Instructions

New order

Place a new order. Weight: 1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
IOCNoImmediate-or-cancel flag
sideYesOrder direction
sizeNoOrder quantity (required for LIMIT orders and MARKET sell orders)
typeYesOrder type
priceNoOrder price (required for LIMIT orders)
amountNoOrder amount (required for MARKET buy orders)
symbolYesTrading pair symbol
clientOrderIdNoClient order ID (alphanumeric and hyphen, max 64 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds only the rate-limit cost ("Weight: 1") and says nothing about authentication, rejected/partially-filled orders, or side effects on balances — minimal added value for a real-money trading mutation.

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

Conciseness3/5

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

Two short lines with no filler and the action is front-loaded, but the extreme brevity is under-specification rather than disciplined conciseness for a tool with 8 parameters and destructive semantics.

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

Completeness2/5

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

For a destructive, non-idempotent order-placement tool with 8 parameters, no output schema, and no guidance on the conditional parameter requirements (price/size for LIMIT, amount for MARKET buy), the description omits nearly everything an agent needs beyond the schema's field-level docs.

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 every parameter (symbol, side, type, price, size, amount, IOC, clientOrderId) is already documented in the schema. The description contributes nothing beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Place a new order"), which is clear enough at a high level, but it is essentially a restatement of the title "New order" with no scope detail and no differentiation from siblings such as pionex_orders_new_multiple_orders or the bot order-creation tools.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives (e.g. bulk vs single order, spot vs grid bots). The agent must infer routing entirely from the tool name.

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