Skip to main content
Glama
Sign In
MCP Pionex Management

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create smart copy order

pionex_bot_create_smart_copy_order
Destructive

Create a new smart copy bot order on Pionex to copy trades, defining portfolio allocations, leverage, total investment, and optional stop-loss or take-profit rules.

Instructions

Create smart copy order

Create a new smart copy bot 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": {
      "base": "<base>",
      "quote": "<quote>",
      "bu_order_data": "<bu_order_data>"
    },
    "name": "pionex_bot_create_smart_copy_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesBase currency (e.g. BTC)
noteNoOptional order note
quoteYesQuote currency (e.g. USDT)
key_idNoAPI Key ID. Optional — derived from the API key used for authentication when omitted.
copy_fromNoSource order ID to copy from (for copy trade orders)
copy_typeNoCopy type identifier
bu_order_dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the safety profile (destructiveHint=true, openWorldHint=true, idempotentHint=false), so the description is not the sole carrier here. It adds the API rate-limit cost ('Weight: 1'), which is genuine behavioral information not present in annotations, but it says nothing about funds being committed or the consequences of the destructive create.

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?

Very short, which is good, but the first sentence is a verbatim copy of the title and the second restates the same purpose, so two of three lines are redundant. Only 'Weight: 1' carries new information, meaning little of the text earns its place.

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?

This is a complex, nested, destructive creation tool with no output schema and 7 parameters, yet the description explains none of the portfolio/investment semantics, no validation step, and no post-create behavior. For a live trading-bot creation endpoint, the description is materially under-specified.

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 86%, so the schema already documents base/quote/bu_order_data and the nested portfolio fields in detail. The description adds no parameter meaning whatsoever, 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 ('Create') and resource ('smart copy bot order'), and the 'smart copy' qualifier implicitly separates it from the grid-order creation siblings. It stops short of naming or routing against those siblings, so it is clear but not fully differentiating.

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 or when-not-to-use guidance. In particular it never mentions the sibling pionex_bot_check_smart_copy_params, which an agent would plausibly need to validate parameters before creating a live bot, nor does it state prerequisites such as funded balance or a source signal.

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