SiteCheck Crypto & Finance

Bitget spot ticker for one pair: last price, bid/ask, 24h

finance_bitget_tickers

Read-only

Bitget spot ticker for one pair (e.g. BTCUSDT): last price, bid/ask, 24h high/low, volumes and 24h change, from Bitget's public v2 market endpoint. Related tools on this server, for a different need: finance_bitstamp_tickers when you need Bitstamp spot ticker for one pair: last, 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": {
      "symbol": "<symbol>"
    },
    "name": "finance_bitget_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Bitget spot symbol, e.g. BTCUSDT, ETHUSDT

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: a per-call cost of $0.002 USDC via x402 on Base/Solana/Arc and the fact that failed calls are not charged — cost and billing semantics are not in the annotations. It does not mention rate limits or freshness/caching, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The returned fields and source are front-loaded in the first sentence, with routing and pricing following in logical order. The sibling routing sentence is somewhat long and enumerates fields of other tools that are irrelevant to calling this one, which is the only real waste.

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 an output schema present, return-value documentation is not required, and the description still summarizes the payload fields. Payment/auth requirements are disclosed, which is unusually complete for a metered API. Only secondary operational details (rate limits, data freshness, symbol-not-found behavior) are absent.

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% for the single 'symbol' parameter, and the schema already supplies the BTCUSDT/ETHUSDT examples. The description reinforces 'for one pair' and the Bitget-specific symbol convention, but adds no syntax or format detail beyond the schema, so the 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?

The description gives a specific verb+resource ('Bitget spot ticker for one pair'), enumerates the exact fields returned (last, bid/ask, 24h high/low, volumes, 24h change) and names the upstream endpoint (public v2 market). It also names the sibling exchanges (Bitstamp, Bitfinex) it is not, so an agent can route on exchange without opening schemas.

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?

It explicitly routes to alternatives ('finance_bitstamp_tickers when you need Bitstamp...', 'finance_bitfinex_tickers when you need Bitfinex spot ticker for one or more pairs'), which gives a clear selection rule by exchange and by single-vs-multi pair. It stops short of stating when this tool should NOT be used (e.g. historical candles or orderbook depth), so no explicit exclusions.

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?