Skip to main content
Glama

Crypto price

crypto_price
Read-onlyIdempotent

Crypto price. Crypto token price in USD read on chain from Chainlink price feeds on Ethereum: up to 5 tickers per call (ETH, BTC, SOL, BNB, LINK...), each with feed address, round id and age. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
symbolsYesone to five tickers, comma-separated, e.g. ETH,BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnly/destructive/idempotent annotations, it discloses the real cost ($0.001 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the unauthenticated-first-call behavior, and the per-ticker return contents (feed address, round id, age). That is precisely the payment-flow context an agent cannot infer from annotations.

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?

Content is front-loaded: purpose, source, limits, cost, then the call sequence. The payment sentence is long and runs three ideas together (cost, currencies, procedure), costing a point, but no sentence is filler.

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 no output schema, the description carries the return-shape burden and does so (per-ticker feed address, round id, age). For a metered, paid, two-call tool it covers cost, authorization flow, limits, and output well enough for an agent to invoke it correctly on the first attempt.

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 earns a bump by explaining the meaning of `payment` operationally — it is the output of the get-terms/sign cycle, not a static credential — and by restating the one-to-five ticker limit for `symbols` in context of the returned feed data.

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?

The description names a specific action and resource — USD token prices read on-chain from Chainlink feeds on Ethereum — plus concrete constraints (max 5 tickers, per-call price, returned fields). The named price source and chain implicitly separate it from the other price siblings (arc_price, base_token_price, xnt_price, commodity_price) without needing to name them.

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?

It gives an explicit two-step procedure: call once without `payment` to obtain terms, sign them with your own wallet, then call again with the payment payload. What's missing is guidance on choosing this tool over the other price tools when several could return a token price.

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