Skip to main content
Glama
Sign In
MCP Pionex Management

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get bot order list

pionex_bot_get_bot_orders
Read-onlyIdempotent

Retrieve bot orders filtered by order type, status, or trading pair. Supports pagination for result navigation.

Instructions

Get bot order list

Query bot order list with optional filters by order type, status, and trading pair. Supports pagination. Weight: 1.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pionex_bot_get_bot_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency filter (e.g. BTC)
quoteNoQuote currency filter (e.g. USDT)
statusNoOrder status filter: `running` - Running orders (default), `finished` - Closed/cancelled orders running
pageTokenNoPagination token (from `nextPageToken` or `previousPageToken` in response)
buOrderTypesNoOrder type filter. Can pass multiple values. If omitted, returns all types. Supported values: `futures_grid`, `future_hedge_grid` (Cross Margin Futures Grid), `spot_grid`, `smart_copy`.

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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes beyond them usefully by disclosing pagination support and the rate-limit cost ('Weight: 1'), which an agent cannot get from the annotations.

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?

Short and front-loaded: the verb+resource leads, followed by filters and pagination/weight in two compact sentences. The only waste is the title restated as the opening line, a minor redundancy.

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 and no required parameters, the description covers what an agent needs: the filter categories and the fact that results are paginated. It would be stronger if it pointed to the response's nextPageToken, but the schema's pageToken description already supplies that link, so the definition is essentially 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 each of the five parameters is fully documented in the schema itself (including the default status and the supported order-type values). The description merely restates the filter categories at a high level, adding no syntax or format detail beyond the schema, so the baseline of 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 ('Get bot order list') and enumerates the filterable fields, so the agent knows it retrieves bot orders rather than a single bot order. It does not explicitly distinguish itself from close siblings like pionex_bot_get_spot_grid_order or pionex_bot_get_futures_grid_order, so sibling differentiation is left implicit.

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?

The phrase 'Query bot order list with optional filters' implies the usage context, and 'Supports pagination' hints at iterative calls, but there is no explicit when-to-use/when-not-to-use guidance or named alternative for fetching a single bot order. Usage is inferable but not spelled out.

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