Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Revoke investment order

pionex_earn_dual_revoke_invest
DestructiveIdempotent

Cancel a pending Dual Investment order before it is matched, provided the order is still unmatched and Earn permission is granted.

Instructions

Revoke investment order

Revokes a pending Dual Investment order before it is matched. Requires Earn permission. Weight: 1.

Parameters are passed as a JSON request body, not query string. Only orders in a pending/unmatched state can be revoked.

Example request body:

{
  "base": "BTC",
  "productId": "BTC-USDXO-260402-68000-P-USDT",
  "clientDualId": "my-order-001"
}

Example response:

{
  "result": true,
  "data": {
    "clientDualId": "my-order-001"
  },
  "timestamp": 1775027817297
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency
productIdYesProduct ID of the order to revoke
clientDualIdYesClient-assigned dual investment order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds valuable context: it requires 'Earn' permission, has 'Weight: 1', and specifies the pending/unmatched state precondition. This goes beyond what the annotations provide.

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?

The description is front-loaded with the core action and key constraints (state, permission, weight). The inclusion of example request and response bodies is helpful but makes the description longer than strictly necessary for the core message.

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?

For a mutation tool with no output schema, the description covers the crucial prerequisites (pending state, Earn permission). The example response clarifies the return shape, compensating for the lack of a formal output schema. It could mention reversibility or error cases, but is largely 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 description coverage is 100%, so the schema fully documents the three parameters. The description's example JSON body provides usage context but does not add new semantic meaning to the parameters themselves. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose5/5

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

States a specific verb (revoke) and resource (a pending Dual Investment order), and clarifies the state constraint ('before it is matched'). This distinguishes it from sibling tools like pionex_earn_dual_invest and pionex_earn_dual_collect.

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

Usage Guidelines4/5

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

Provides a clear condition for use: 'Only orders in a pending/unmatched state can be revoked.' It doesn't explicitly name alternatives (e.g., what to do if the order is already matched), but the state constraint gives strong contextual guidance.

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