Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get underlying index price

pionex_earn_dual_index
Read-onlyIdempotent

Fetches the real-time index price for a Dual Investment underlying asset using base and quote symbols, providing the settlement reference price to check strike status.

Instructions

Get underlying index price

Returns the real-time index price for a Dual Investment underlying asset. Weight: 1.

Both base and quote are required. Works for both USDT and USDXO quoted pairs.

The index price is the reference price used at settlement to determine whether the strike price was hit.

Example request (USDXO pair):

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

Example request (USDT pair):

GET /api/v1/earn/dual/index?base=LRC&quote=USDT

Example response:

{
  "result": true,
  "data": {
    "index": "69142.6",
    "base": "BTC",
    "quote": "USDXO",
    "updateTime": 1775025942486
  },
  "timestamp": 1775025942754
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the safety profile needs no restating. The description adds genuine context beyond them: the index price's settlement role, the weight (1), and a full example response body, which is useful since no output schema exists.

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?

Purpose is front-loaded, followed by constraints and then worked examples. The content is slightly long but the example requests and response earn their place; there is little redundancy.

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?

For a simple two-parameter read tool with no output schema, the description supplies the response shape via a concrete example, the scoping constraints, and the semantic meaning of the returned value. An agent has everything needed to call and interpret it.

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 both parameters and the quote enum/rule ('USDXO for BTC/ETH, USDT otherwise') are already documented. The description's example requests reinforce the pairing convention but add no syntax meaning beyond what the schema states, so the baseline 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?

The description states a specific verb+resource ('Get underlying index price') and clarifies it returns the real-time index price for a Dual Investment underlying asset. It explains the role of the value (settlement reference for strike-hit determination), but does not differentiate itself from nearby siblings like pionex_earn_dual_prices or pionex_earn_delivery_prices.

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 specifies that both base and quote are required and that it works for USDT and USDXO quoted pairs, with example requests for each. However, it never states when to choose this tool over siblings such as pionex_earn_dual_prices or pionex_earn_delivery_prices, so the usage context is only implied.

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