Skip to main content
Glama

USD spot prices for up to 20 symbols from Coinbase

crypto_price
Read-only

USD spot prices for up to 20 symbols (BTC, ETH, SOL...) from Coinbase, with the source of each price. A Solana mint address also works and is priced by Jupiter. Symbols without a price are listed in unavailable. Cached 15 seconds. 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_convert when you need to convert crypto and fiat amounts at the current spot rate. 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": {
      "symbols": "<symbols>"
    },
    "name": "crypto_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesComma-separated symbols (BTC,ETH) or Solana mint addresses, up to 20

Output Schema

NameRequiredDescriptionDefault
pricesNo
sourceNo
checkedAtNo
disclaimerNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses cache TTL (15 seconds), fallback behavior for unpriced symbols ('listed in unavailable'), the Jupiter pricing path for Solana mints, and a full cost model ($0.002 per successful call via x402, failures not charged). That is exactly the operational context annotations cannot carry.

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 purpose and scope, then constraints, then sibling routing, then cost. Dense but organized; the 'not financial advice' line is boilerplate but brief enough not to bloat.

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?

With a single required parameter, an output schema, and read-only annotations, the description still covers everything an agent needs to decide and call: scope, input flavors, caching, the unavailable bucket, cost, and alternatives. Nothing material is missing.

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% and already documents comma-separated symbols and the 20-symbol cap, so the baseline is 3. The description still adds meaning by stating that Solana mint addresses are accepted and are priced by Jupiter rather than Coinbase, which clarifies per-input source routing.

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 resource and scope: 'USD spot prices for up to 20 symbols (BTC, ETH, SOL...) from Coinbase, with the source of each price.' It also flags the mint-address variant, so the agent knows exactly what the tool returns without opening the 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 away from two siblings with conditions: 'crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m' and 'crypto_convert when you need to convert crypto and fiat amounts at the current spot rate.' No inference required.

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