Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Crypto price in USD

crypto_price
Read-only

Crypto price in USD: live spot price for a cryptocurrency symbol (ETH, BTC, USDC, SOL, …) with timestamp and source. Source: Coinbase public spot price, fallback Kraken public ticker. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/crypto/price

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": "crypto_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker symbol, e.g. ETH, BTC, USDC, SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), but the description adds genuinely useful behavior: the upstream data sources (Coinbase with Kraken fallback), the fact that responses carry a timestamp and source, and — critically — that each call costs $0.001 USDC via x402 on Base with a free demo available. What is missing is failure behavior for unknown or unsupported tickers.

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?

One front-loaded clause states what it returns, followed by source, pricing, and demo link — no filler. The pricing and demo sentences are extra weight but earn their place for a paid endpoint; only the demo URL feels marginally promotional.

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 read tool with no output schema, the description covers inputs, data provenance, response fields (timestamp, source), and cost. The remaining gap is error/edge-case behavior for invalid or unsupported symbols, which an agent would otherwise have to discover empirically.

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?

The schema has 100% description coverage for the single required parameter, including its pattern and examples, so the schema carries the burden and baseline would be 3. The description reinforces the semantics by listing concrete ticker values inline, making the expected symbol form clear at a glance without adding new constraints.

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 and resource — retrieving the live spot price in USD for a cryptocurrency symbol — and names the concrete examples (ETH, BTC, USDC, SOL). It is immediately distinguishable from siblings like eth_token_balance or base_tx, which concern balances and transactions rather than market price.

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 only implied: an agent can infer this is the tool for price lookups, and the cost and free-demo link help it decide whether to call. However, there is no explicit when-to-use versus alternative guidance, no statement about which symbols are supported beyond examples, and no exclusion conditions.

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