SiteCheck Crypto & Finance

WhiteBIT exchange spot ticker for one market: last price

finance_whitebit_tickers

Read-only

WhiteBIT exchange spot ticker for one market (e.g. BTC_USDT): last price, 24h change and volumes, from WhiteBIT's public v4 ticker list. Related tools on this server, for a different need: finance_bitget_tickers when you need Bitget spot ticker for one pair: last price, bid/ask, 24h; finance_bitfinex_tickers when you need Bitfinex spot ticker for one or more pairs: bid, ask, last. 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": {
      "market": "<market>"
    },
    "name": "finance_whitebit_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`market`	Yes	WhiteBIT market, e.g. BTC_USDT, ETH_USDT

Output Schema

Name	Required	Description	Default
`last`	No
`frozen`	No
`market`	No
`source`	No
`checkedAt`	No
`baseVolume24h`	No
`quoteVolume24h`	No
`changePercent24h`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnly/openWorld annotations: a concrete cost model ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and the key billing rule that failed calls are not charged. It also discloses the data origin (public v4 ticker list), which matters for freshness/trust. None of this is derivable from annotations or 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?

One front-loaded sentence establishes purpose and payload, then sibling routing, then pricing — a sensible order with no filler. It is dense (semicolon-chained clauses) but every sentence carries information the agent needs; minor tightening would improve readability.

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?

For a one-parameter read tool with an output schema and readOnly annotations, the description covers purpose, alternatives, data source and payment mechanics. Remaining gaps are small: behavior on an invalid/unknown market and whether the ticker is real-time vs cached are 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 description coverage is 100% and the single 'market' parameter is already documented with the same BTC_USDT/ETH_USDT example. The description's '(e.g. BTC_USDT)' restates the schema rather than adding format rules such as case sensitivity or separator requirements, 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 a specific verb-less but precise resource: 'WhiteBIT exchange spot ticker for one market (e.g. BTC_USDT)', enumerating the returned fields (last price, 24h change, volumes) and the upstream source (public v4 ticker list). An agent can immediately tell this is the WhiteBIT single-market ticker, distinct from the Bitget and Bitfinex tickers named later.

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?

Explicitly routes to alternatives: 'finance_bitget_tickers when you need Bitget spot ticker... finance_bitfinex_tickers when you need Bitfinex...'. This gives clear when-to-use-another guidance for the exchange choice. It does not state exclusions for this tool itself (e.g. multi-market queries, unsupported markets), so it falls just short of the top score.

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?