SiteCheck Crypto & Finance

Coinbase Exchange order book for one product: best bid

crypto_coinbase_spot_exchange

Read-only

Coinbase Exchange (US spot) order book for one product: best bid and ask, spread, USD depth within 1% and 2% of mid (aggregated level-2 levels only), 24h base volume, 24h RFQ (institutional request-for-quote) volume, last price and 24h high/low. Coinbase Exchange data only, not Coinbase Advanced or other venues. Related tools on this server, for a different need: finance_coinbase_exchange_products when you need Coinbase Exchange trading products with status and minimum; finance_coinbase_orderbook_candles when you need Coinbase Exchange OHLCV candles for one product at 1m, 5m. 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": {
      "product": "<product>"
    },
    "name": "crypto_coinbase_spot_exchange"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes	Coinbase product id such as BTC-USD or ETH-USD

Output Schema

Name	Required	Description	Default
`last`	No
`low24h`	No
`source`	No
`bestAsk`	No
`bestBid`	No
`high24h`	No
`open24h`	No
`product`	No
`midPrice`	No
`checkedAt`	No
`spreadPct`	No
`bookSequence`	No
`volume24hBase`	No
`volume30dBase`	No
`depthWithin1pct`	No
`depthWithin2pct`	No
`rfqVolume24hBase`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/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 added value is the pricing model: $0.002 in USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged. It also discloses that depth figures come from aggregated level-2 levels only, which materially affects interpretation of the numbers. Lacks any note on rate limits or data staleness.

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?

Purpose and returned metrics are front-loaded, then exclusions, then sibling routing, then pricing – a sensible order. The metric enumeration is long but each item is substantive; the pricing sentence compresses several facts without filler.

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 tool with a full output schema, the description covers the remaining unknowns: venue coverage, aggregation basis for depth, per-call cost, payment rails, and alternatives for adjacent needs. An agent has everything required to decide and invoke correctly.

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 parameter already documents the Coinbase product id format with BTC-USD/ETH-USD examples. The description only reinforces the 'one product' constraint and adds no additional syntax, casing, or validity rules beyond what the schema states.

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 resource (Coinbase Exchange spot order book for one product) and enumerates the exact content returned: best bid/ask, spread, USD depth within 1% and 2% of mid, 24h volume, RFQ volume, last price and 24h high/low. It also explicitly scopes itself away from Coinbase Advanced and other venues, so an agent can distinguish it from the many sibling order book tools.

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 two adjacent needs to named siblings (finance_coinbase_exchange_products for product listings, finance_coinbase_orderbook_candles for OHLCV) and constrains data scope to Coinbase Exchange. It does not, however, say when a different venue's order book (e.g. crypto_binance_orderbook_depth) should be preferred, so venue selection guidance is only partially covered.

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?