SiteCheck Crypto & Finance

Gemini crypto exchange public ticker for one market: bid

finance_gemini_tickers

Read-only

Gemini crypto exchange public ticker for one market (e.g. btcusd): bid, ask, last price and 24h volume. Market data only; no order book or history. Related tools on this server, for a different need: finance_whitebit_tickers when you need WhiteBIT exchange spot ticker for one market: last price; 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_gemini_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Gemini market, lowercase, e.g. btcusd, ethusd

Output Schema

Name	Required	Description	Default
`ask`	No
`bid`	No
`last`	No
`source`	No
`symbol`	No
`checkedAt`	No
`updatedAt`	No
`volume24h`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses non-obvious operational facts: a $0.002 USDC per-successful-call charge, the x402 payment rails (Base, Solana, Arc), and that failed calls are not billed. Cost and billing behavior is exactly the kind of context an agent cannot infer from structured fields.

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?

Scope and returned fields are front-loaded, then usage boundaries, then cost. Every sentence carries load, though the pricing sentence is long and slightly detours into payment-rail detail that could be tighter.

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 single-parameter read-only ticker with an output schema, the description need not explain return values. What an agent does need — scope limits, sibling routing, and cost/payment mechanics — is all present.

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 single parameter already documents lowercase formatting with examples (btcusd, ethusd). The description reinforces the "one market" constraint and repeats the example, adding marginal meaning beyond the schema, so the baseline 3 is appropriate.

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 opens with a specific verb and resource ("Gemini crypto exchange public ticker for one market") and enumerates the exact returned fields (bid, ask, last, 24h volume). It is immediately distinguishable from siblings like finance_whitebit_tickers and finance_bitfinex_tickers, which are also named.

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?

It states the boundary explicitly ("Market data only; no order book or history") and routes the agent to named alternatives with the condition that selects each one (WhiteBIT for last-price-only, Bitfinex for multi-pair bid/ask/last). This is an explicit when-to-use/when-not/alternatives disclosure.

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?