SiteCheck Crypto & Finance

Bitstamp spot ticker for one pair: last, bid, ask, 24h

finance_bitstamp_tickers

Read-only

Bitstamp spot ticker for one pair (e.g. btcusd, btceur): last, bid, ask, 24h open/high/low, volume and VWAP, from Bitstamp's public 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_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": {
      "pair": "<pair>"
    },
    "name": "finance_bitstamp_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`pair`	Yes	Bitstamp pair in lowercase, e.g. btcusd, ethusd, btceur

Output Schema

Name	Required	Description	Default
`ask`	No
`bid`	No
`low`	No
`high`	No
`last`	No
`pair`	No
`source`	No
`open24h`	No
`vwap24h`	No
`checkedAt`	No
`updatedAt`	No
`volume24h`	No
`changePercent24h`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/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 description's job is to add context. It does: public endpoint, exact price ($0.002 USDC per successful call via x402 on Base/Solana/Arc), and the billing guarantee that failed calls are not charged — a genuinely non-obvious trait for an agent deciding whether to retry. It doesn't discuss rate limits or error behavior, keeping it short of 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?

Front-loaded with the core capability and return fields, then alternates, then pricing — a sensible order. The sibling enumeration is somewhat repetitive ('when you need X spot ticker for ...'), but each clause carries routing value rather than padding.

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 one-parameter read-only ticker with an output schema and full schema coverage, everything an agent needs is present: scope, returned fields, exchange identity, alternatives, and cost model. No return-value explanation is required given the output schema.

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 'pair' parameter already documents lowercase format with examples (btcusd, ethusd, btceur). The description repeats the same examples (btcusd, btceur) without adding constraint meaning 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 a specific verb+resource combination ('Bitstamp spot ticker for one pair') and enumerates exactly what is returned (last, bid, ask, 24h open/high/low, volume, VWAP). It also names the sibling tools it is not, so an agent can distinguish it from finance_bitget_tickers and finance_bitfinex_tickers without opening any 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 the agent: use this for Bitstamp, use finance_bitget_tickers for Bitget, use finance_bitfinex_tickers for Bitfinex (including multi-pair). The selection condition is stated per alternative rather than left to inference.

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?