Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get user balances

pionex_earn_dual_balances
Read-onlyIdempotent

Retrieve your Dual Investment account balances from Pionex. View free and frozen amounts per coin, with optional merging of balances across base currencies.

Instructions

Get user balances

Returns the authenticated user's Dual Investment account balances. Requires View permission. Weight: 1.

Example request:

GET /api/v1/earn/dual/balances?timestamp=1774959429596

Example response:

{
  "result": true,
  "data": {
    "balances": [
      {
        "base": "BTC",
        "coin": "USDT",
        "free": "100.00",
        "frozen": "50.00",
        "updateTime": 1774959429596
      }
    ]
  },
  "timestamp": 1774959429596
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mergeNoWhen `true`, merges balances with the same coin across different base currencies

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the 'View' permission requirement and weight, which is extra context. However, it doesn't describe pagination, rate limits, or the merge parameter behavior beyond the schema.

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?

The description is front-loaded with the core purpose, then includes example request/response. The examples take space but provide concrete value for an agent. No wasted sentences, though the JSON example is somewhat 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?

Given no output schema, the example response compensates by illustrating the return structure. The permission requirement and weight are included. Missing details like error cases or pagination are minor for a simple balance retrieval tool.

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 parameter 'merge' is fully documented in the schema. The description doesn't add any parameter details, which is acceptable given high coverage. 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?

The description clearly states it returns the authenticated user's Dual Investment account balances, which is a specific verb and resource. It doesn't explicitly differentiate from sibling tools like pionex_account_get_balance or pionex_wallet_get_balance_full, but the 'Dual Investment account' qualifier implicitly scopes it.

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 mentions requiring 'View' permission, which is useful, but doesn't say when to use this tool versus alternatives like pionex_earn_arbitrage_fetch_user_balances or other balance tools. No explicit when-not-to-use guidance.

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