Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get historical delivery prices

pionex_earn_delivery_prices
Read-onlyIdempotent

Retrieve historical settlement delivery prices for a Dual Investment pair to determine payout direction at expiry. Filter by base currency and optional quote.

Instructions

Get historical delivery prices

Returns historical settlement delivery prices for a Dual Investment pair. Weight: 1.

The delivery price is the index price recorded at the exact moment of each product's expiry, used to determine the settlement direction (base or quote currency payout).

base is required. quote is optional but recommended to narrow results — use USDXO for BTC/ETH pairs and USDT for all other base currencies.

Example request (BTC/USDXO):

GET /api/v1/earn/dual/deliveryPrices?base=BTC&quote=USDXO

Example request (XRP/USDT):

GET /api/v1/earn/dual/deliveryPrices?base=XRP&quote=USDT

Example response:

{
  "result": true,
  "data": {
    "prices": [
      {
        "delivery": "69142.6",
        "date": "2026-04-01",
        "deliveryTime": 1775030400000
      }
    ]
  },
  "timestamp": 1775026529937
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency (e.g. `BTC`, `XRP`)
quoteNoQuote currency filter. Use `USDXO` for BTC/ETH pairs; use `USDT` for all other base currencies.
endTimeNoEnd timestamp in milliseconds
startTimeNoStart timestamp in milliseconds

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 the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral context beyond that: the 'Weight: 1' rate-limit cost, the definition of a delivery price, and a concrete example response shape. It does not explain time-range defaults or pagination, so it stops short of a 5.

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?

Purpose and the delivery-price definition are front-loaded well, but the body carries two near-identical example requests plus a full example response, which is more verbose than needed for four parameters. The repetition costs space without adding proportional value.

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 description usefully includes an example response showing the prices/date/deliveryTime fields, which an agent needs to interpret results. It omits any statement about how startTime/endTime affect the result set or default behavior, leaving a modest gap.

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 coverage is 100%, so the schema already documents base, quote, startTime, and endTime. The description restates that base is required and quote optional/recommended with the USDXO-vs-USDT rule, which largely duplicates the schema text rather than adding new semantics. 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?

States a specific verb and resource ('Get historical delivery prices') and then defines what a delivery price actually is (the index price at expiry, used to determine settlement direction). This makes it distinguishable from sibling tools like pionex_earn_dual_prices and pionex_earn_dual_index, though it never names those alternatives outright.

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?

It gives practical guidance on parameter values (quote optional but recommended; USDXO for BTC/ETH, USDT for others), which is useful. However, it never states when to choose this tool over sibling price-related tools such as pionex_earn_dual_prices, so usage is implied rather than contrasted.

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