SiteCheck Crypto & Finance

Phemex perpetual-contract ticker for one symbol: last

finance_phemex_tickers

Read-only

Phemex perpetual-contract ticker for one symbol (e.g. BTCUSDT): last price, mark and index price, funding rate, open interest and 24h volume, from Phemex's public md/v2 endpoint. Related tools on this server, for a different need: finance_bitfinex_tickers when you need Bitfinex spot ticker for one or more pairs: bid, ask, last; finance_bitget_tickers when you need Bitget spot ticker for one pair: last price, bid/ask, 24h. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "finance_phemex_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Phemex contract symbol, e.g. BTCUSDT

Output Schema

Name	Required	Description	Default
`last`	No
`open`	No
`low24h`	No
`source`	No
`symbol`	No
`high24h`	No
`checkedAt`	No
`markPrice`	No
`volume24h`	No
`indexPrice`	No
`fundingRate`	No
`turnover24h`	No
`openInterest`	No
`predictedFundingRate`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnly/openWorld, but the description adds the data provenance (Phemex public md/v2 endpoint) and, unusually, the cost model: $0.002 per successful call via x402 on Base/Solana/Arc, with failures uncharged. That is genuinely useful call-planning context. It stops short of saying whether the ticker is a live snapshot or cached, which is the remaining behavioral gap.

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-loads the core purpose, then sibling routing, then pricing — a sensible order for an agent. The pricing clause is the longest part but earns its place as decision-relevant information; the 'Related tools on this server, for a different need' framing is slightly formulaic.

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?

One required parameter, an output schema, and readOnly annotations mean little else is needed; the description covers purpose, alternatives, data source, and cost. Only the freshness/caching behavior of the ticker is left unstated.

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% and the schema already documents the sole parameter with the example BTCUSDT. The description only repeats that example in passing, adding no format or constraint detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (Phemex perpetual-contract ticker), the scope (one symbol), and enumerates the returned fields (last, mark, index price, funding rate, open interest, 24h volume) plus the upstream endpoint (md/v2). An agent can distinguish it from the neighboring spot ticker tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to alternatives: finance_bitfinex_tickers for multi-pair Bitfinex spot, finance_bitget_tickers for Bitget spot, with the field differences spelled out, making the selection decision trivial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?