Skip to main content
Glama

A level-2 order book snapshot for a Coinbase pair: best bid

crypto_orderbook
Read-only

A level-2 order book snapshot for a Coinbase pair: best bid and ask, mid price, spread in price and basis points, and the top bids and asks up to depth 50. It is a snapshot, not a quote: prices move between calls. Information only, not financial advice. Related tools on this server, for a different need: crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m; crypto_indicators when you need Technical indicators for one crypto pair and interval. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); 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": "crypto_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoinbase product, e.g. BTC-USD
depthNo1 to 50 levels per side (default 10)

Output Schema

NameRequiredDescriptionDefault
midNo
asksNo
bidsNo
pairNo
depthNo
sourceNo
spreadNo
bestAskNo
bestBidNo
checkedAtNo
spreadBpsNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, and the description adds genuinely new behavior: results are point-in-time and go stale between calls, and pricing is $0.002 per successful call with failed calls uncharged — useful for cost-aware planning. It does not spell out rate limits or response size, so it stops short of the top mark.

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 content are front-loaded in the first sentence, followed by routing alternatives and pricing, so ordering is strong. However, the 'Information only, not financial advice' disclaimer and the restated sibling titles add padding that does not help selection.

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?

An output schema exists, so return values need not be described; the description instead covers what matters for this tool: snapshot semantics, cost model, and sibling routing. Nothing an agent needs to call it correctly appears to be missing.

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%, so pair (Coinbase product like BTC-USD) and depth (1–50, default 10) are already documented. The description only echoes the depth-50 ceiling and the Coinbase-pair restriction, adding little beyond the schema; 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 resource and verb-like outcome (level-2 order book snapshot for a Coinbase pair) and enumerates contents: best bid/ask, mid, spread in price and bps, top levels up to depth 50. It also distinguishes itself from siblings crypto_candles and crypto_indicators by naming each and its different output.

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 crypto_candles for OHLCV candles at 1m/5m/15m, crypto_indicators for technical indicators on a pair+interval. It also implicitly states when this tool is right (order book depth/spread) and warns it is a snapshot, not a quote.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources