Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get product prices

pionex_earn_dual_prices
Read-onlyIdempotent

Fetch Dual Investment product prices and yield rates to verify investability and get the profit value needed for orders.

Instructions

Get product prices

Returns the latest yield rate and investability status for Dual Investment products. Weight: 1.

All three parameters are required: base, quote, and productIds. Omitting any one of them will return a DUAL_PARAMETER_ERROR.

productIds is a comma-separated list of product IDs. Works for both USDT and USDXO quoted pairs.

When canInvest is false, profit and baseSize will be empty strings.

Workflow note: Always call this endpoint before placing an order. The profit value returned here must be passed as-is to POST /api/v1/earn/dual/invest. Submitting a stale or mismatched profit will be rejected.

Example request (USDT pair):

GET /api/v1/earn/dual/prices?base=LRC&quote=USDT&productIds=LRC-USDT-260410-0.03-C-USDT,LRC-USDT-260410-0.02-C-USDT

Example request (USDXO pair):

GET /api/v1/earn/dual/prices?base=ETH&quote=USDXO&productIds=ETH-USDXO-260410-3000-C-USDT,ETH-USDXO-260410-2900-C-USDT

Example response:

{
  "result": true,
  "data": {
    "products": [
      {
        "productId": "LRC-USDT-260410-0.02-C-USDT",
        "canInvest": true,
        "profit": "0.01242",
        "baseSize": "8000000",
        "updateTime": 1775026225630
      },
      {
        "productId": "LRC-USDT-260410-0.03-C-USDT",
        "canInvest": false,
        "profit": "0",
        "baseSize": "",
        "updateTime": 0
      }
    ]
  },
  "timestamp": 1775026244892
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency (e.g. `BTC`, `ETH`, `LRC`)
quoteYesQuote currency. Use `USDXO` for BTC/ETH pairs; use `USDT` for all other base currencies.
productIdsYesComma-separated product ID list. Multiple IDs are supported (e.g. `ETH-USDXO-260410-3000-C-USDT,ETH-USDXO-260410-2900-C-USDT`). Obtain IDs from `/openProducts`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it documents the DUAL_PARAMETER_ERROR on missing params, the empty-string behavior of `profit`/`baseSize` when `canInvest` is false, and the rejection of stale/mismatched `profit` values. These are real behavioral constraints an agent needs before calling.

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 purpose, then constraints, then workflow, then examples. The two request examples and full response JSON are verbose but directly useful for a tool with no output schema; a bit of tightening is possible but nothing is wasted outright.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by showing a full example response and explaining field-level semantics (`canInvest`, `profit`, `baseSize`, `updateTime`). Combined with the required-parameter and workflow notes, an agent has everything needed to call and interpret this correctly.

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 description coverage is 100%, so baseline is 3, but the description adds value: it stresses that all three parameters are mandatory, that `productIds` is a comma-separated list, and that quoting differs between USDT and USDXO pairs (reinforcing the schema's enum guidance).

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: retrieves the latest yield rate and investability status for Dual Investment products, keyed by base/quote/productIds. This is clearly distinguishable from generic market data siblings, though it does not explicitly contrast itself with the nearby `pionex_earn_dual_products`/`dual_symbols` endpoints.

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?

Gives a concrete workflow directive ('Always call this endpoint before placing an order') and explains that the returned `profit` must be passed as-is to the invest endpoint, plus where to source productIds (`/openProducts`). Clear context, though it does not explicitly rule out when this endpoint is unnecessary.

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