Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List supported trading pairs

pionex_earn_dual_symbols
Read-onlyIdempotent

List supported Dual Investment trading pairs, optionally filtered by base currency, to identify valid pairs and limits for Earn orders.

Instructions

List supported trading pairs

Returns all trading pairs supported by Dual Investment, optionally filtered by base currency. Weight: 1.

Supported quote currencies include: USDT, USDC, USD, USDXO.

Example request:

GET /api/v1/earn/dual/symbols?base=BTC

Example response:

{
  "result": true,
  "data": {
    "coins": [
      {
        "base": "BTC",
        "quote": "USDT",
        "currency": "USDT",
        "basePrecision": 8,
        "currencyPrecision": 8,
        "baseMin": "0.00001",
        "currencyMin": "1",
        "baseMax": "80",
        "currencyMax": "2000000"
      }
    ]
  },
  "timestamp": 1774959429596
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoBase currency filter (e.g. `BTC`, `ETH`). Omit to return all supported pairs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and openWorld. The description adds useful context: the weight metric, supported quote currencies, and a full example response including precision and min/max fields. This goes beyond what annotations provide, though it doesn't discuss rate limits or caching.

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?

Front-loaded with the purpose and weight, but then includes a full example response JSON with nested fields that are not strictly necessary for an agent to call the tool. The example response is useful for understanding output but adds length. Overall structure is clear but verbose.

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 simple list tool with no output schema, the description provides adequate context: what it lists, optional filter, supported currencies, and an example response. It misses when-to-use guidance and sibling differentiation, but otherwise complete enough for an agent to call correctly.

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 already documents the base parameter. The description adds an example request showing base=BTC usage, which reinforces the format, but does not add syntax beyond the schema. Baseline 3 is appropriate.

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?

Clearly states a specific verb+resource: lists supported trading pairs for Dual Investment, scoped to base currency filtering. It does not differentiate itself from sibling tools like pionex_market_get_symbol_info or pionex_earn_dual_products, but the 'Dual Investment' scoping does distinguish it somewhat from market symbol listings.

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?

Provides an example request showing usage with the base filter and states the base param is optional to return all pairs. However, it never says when to use this vs. pionex_market_get_symbol_info or pionex_earn_dual_products, so usage context is implied rather than explicit.

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