Skip to main content
Glama

OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m

crypto_candles
Read-only

OHLCV candles for a Coinbase trading pair (BTC-USD) at 1m, 5m, 15m, 1h, 6h or 1d granularity, up to 300, newest first, from Coinbase Exchange public market data. Prices are that venue's trades only; when Coinbase is rate-limited the same candles come from Kraken or Bitstamp and source names the venue. Information only, not financial advice. Related tools on this server, for a different need: crypto_orderbook when you need a level-2 order book snapshot for a Coinbase pair: best bid; 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_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoinbase product, e.g. BTC-USD
limitNo1 to 300 (default 100)
granularityNo1m, 5m, 15m, 1h, 6h or 1d (default 1h)

Output Schema

NameRequiredDescriptionDefault
pairNo
countNo
sourceNo
candlesNo
checkedAtNo
disclaimerNo
granularityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses venue fallback behavior (Kraken or Bitstamp when Coinbase is rate-limited), that the source field names the venue, that prices reflect a single venue's trades, ordering and row cap, and that failed calls are not billed. This is exactly the kind of behavior an agent needs before spending money on a call.

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 purpose and scope, then siblings, then pricing. The pricing sentence is long and the 'not financial advice' note is boilerplate, but overall it is dense without redundancy.

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?

An output schema exists so return-value explanation is unnecessary; the description covers the remaining gaps an agent would care about (fallback source, ordering, row cap, cost). Nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning not in the schema: 'newest first' ordering and the 300-row ceiling, plus the example BTC-USD pair format. Granularity and limit defaults largely duplicate the schema.

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 (OHLCV candles for a Coinbase pair) with scope details: granularity options, max 300, newest-first ordering, and venue source. An agent can immediately tell this is a candlestick/history tool and not an order book or indicator tool.

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 names alternatives and the condition that selects them: crypto_orderbook for a level-2 snapshot and crypto_indicators for technical indicators 'for a different need.' No explicit when-not-to-use for this tool itself, but the routing guidance is clear and actionable.

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