SiteCheck Crypto & Finance

Bitfinex spot ticker for one or more pairs: bid, ask, last

finance_bitfinex_tickers

Read-only

Bitfinex spot ticker for one or more pairs (e.g. tBTCUSD,tETHUSD): bid, ask, last, 24h change and volume, from Bitfinex's public v2 ticker endpoint. 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_bitstamp_tickers when you need Bitstamp spot ticker for one pair: last, 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": {
      "symbols": "<symbols>"
    },
    "name": "finance_bitfinex_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`symbols`	Yes	Comma-separated Bitfinex v2 symbols with t prefix, up to 10 (e.g. tBTCUSD,tETHUSD)

Output Schema

Name	Required	Description	Default
`source`	No
`tickers`	No
`checkedAt`	No

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 and openWorldHint, so the bar is lower, and the description still adds real context: it is a public endpoint (no auth), costs $0.002 USDC per successful call via x402 on Base/Solana/Arc, and failed calls are not charged. It does not discuss rate limits, pagination, or behavior when more than 10 symbols are passed, so it stops short of fully rich disclosure.

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 purpose statement is front-loaded and the pricing sentence is compact and useful. The middle sibling-enumeration sentence is long and reads as templated cross-linking, but it does carry routing value, so nothing is truly wasted.

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 single-parameter read tool with an output schema and safety annotations, the description covers what to pass, what comes back, cost, and alternatives. Only edge behavior at the 10-symbol cap is left implicit, which is a minor gap given the low complexity.

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 schema already specifies comma-separated, t-prefixed symbols with a max of 10. The description only restates the same example (tBTCUSD,tETHUSD) and adds no extra syntax, encoding, or error semantics, so the baseline of 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?

Names a specific verb and resource ('Bitfinex spot ticker for one or more pairs') and enumerates the returned fields (bid, ask, last, 24h change, volume) plus the source endpoint (public v2 ticker). It is clearly distinguishable from the Bitget and Bitstamp ticker siblings by exchange and by supporting multiple pairs.

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 the agent to finance_bitget_tickers and finance_bitstamp_tickers with the condition that selects them ('one pair'), implicitly reserving this tool for multi-pair Bitfinex quotes. There are no explicit when-not-to-use cases beyond the two named siblings, but for an exchange-specific ticker the selection logic is stated clearly enough.

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?