Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List open products

pionex_earn_dual_products
Read-onlyIdempotent

List open Dual Investment products for a specific trading pair and type. Returns product IDs, strike prices, and expiry times to compare available offers.

Instructions

List open products

Returns currently open Dual Investment products for a specific trading pair and type. Weight: 1.

Type semantics:

  • DUAL_BASE: invest in base currency (e.g. BTC); if price rises above strike at expiry, principal + yield are returned in base currency, otherwise converted to quote currency

  • DUAL_CURRENCY: invest in quote/investment currency (e.g. USDT); if price falls below strike at expiry, principal + yield are returned in quote currency, otherwise converted to base currency

Quote currency rules:

  • base=BTC or base=ETH: use quote=USDXO, currency=USDT or USDC

  • All other base currencies: use quote=USDT, currency=USDT

Example request (BTC, DUAL_BASE):

GET /api/v1/earn/dual/openProducts?base=BTC&quote=USDXO&currency=USDT&type=DUAL_BASE

Example request (XRP, DUAL_BASE):

GET /api/v1/earn/dual/openProducts?base=XRP&quote=USDT&currency=USDT&type=DUAL_BASE

Example response:

{
  "result": true,
  "data": {
    "products": [
      {
        "productId": "BTC-USDXO-260401-69000-C-USDT",
        "base": "BTC",
        "quote": "USDXO",
        "currency": "USDT",
        "type": "DUAL_BASE",
        "createTime": 1774686600000,
        "expireTime": 1775030400000,
        "strike": "69000",
        "expired": false
      }
    ]
  },
  "timestamp": 1775025855477
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency (e.g. `BTC`, `ETH`, `XRP`)
typeYes`DUAL_BASE` — invest in base currency; `DUAL_CURRENCY` — invest in quote/investment currency
quoteYesQuote currency. Use `USDXO` for BTC/ETH; use `USDT` for all other base currencies.
currencyNoInvestment currency filter. For BTC/ETH pairs: `USDT` or `USDC`. For other pairs: `USDT`.

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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the 'Weight: 1' rate-limit cost, and the payout mechanics of each type (conversion at expiry above/below strike), which is domain behavior an agent needs to reason about products.

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?

Front-loaded with the core action, then organized into labeled sections (type semantics, quote currency rules, examples). The embedded example response is the only documentation of the return shape since no output schema exists, so it earns its space rather than being padding.

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, the sample response fills the return-value gap, and the type/quote rules fully cover the 4 parameters, so an agent can call this correctly. Minor gaps remain (no mention of result ordering, pagination, or whether expired products can appear) for a list endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by giving explicit quote-currency rules per base asset and two fully worked example requests. This meaningfully reduces the risk of the agent assembling an invalid base/quote/currency combination.

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 ('List/Returns currently open Dual Investment products') scoped to a trading pair and type, which is far more precise than the generic title 'List open products'. It does not explicitly differentiate itself from nearby siblings such as pionex_earn_dual_symbols or pionex_earn_dual_prices, so it falls short of a 5.

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 or when-not-to-use guidance and no routing to alternatives (e.g. dual_symbols, dual_prices). The type and quote-currency rules describe what a product is, not when an agent should call this endpoint rather than a sibling.

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