Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

get_crypto_price

Paid $0.01 (x402, USDC Base): live crypto spot price in USD for a pair like BTC-USD / ETH-USD / SOL-USD. Sourced from Coinbase public price APIs, edge-cached up to 30s.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_crypto_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair BASE-QUOTE, e.g. BTC-USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost and payment rail ($0.01 via x402, USDC on Base), data provenance (Coinbase public price APIs), and a staleness bound (edge-cached up to 30s). It omits failure behavior for unsupported or malformed pairs and any rate/retry limits, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with cost and payment mechanism, then the resource and provenance. No filler and nothing that duplicates the schema.

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?

For a one-parameter lookup with no annotations, the description covers cost, source, freshness, and the returned unit (USD). With no output schema, it could be clearer about the response shape (bare number vs. object with timestamp), which is the only notable gap.

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 parameter already documents the BASE-QUOTE format with a BTC-USD example. The description adds more example pairs (ETH-USD, SOL-USD) but no new format rules or constraints, so it stays at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource — 'live crypto spot price in USD for a pair' — with concrete examples (BTC-USD / ETH-USD / SOL-USD), so an agent knows exactly what it returns. It does not differentiate itself from nearby siblings such as get_coin_convert, get_usd_price, or get_market_pulse, leaving the agent to infer which price tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'live crypto spot price' and the cache note ('edge-cached up to 30s'), which hints at when freshness matters. There is no explicit when-to-use / when-not guidance and no named alternative, despite three sibling tools in the same price/convert space.

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