Skip to main content
Glama

Crypto price, market cap, volume (x402)

crypto_market_metrics

Read-onlyIdempotent

$0.09 via x402: Live Crypto Market Metrics — real-time price, market cap, and 24h volume for cryptocurrencies.

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": {
      "ids": "<ids>"
    },
    "name": "crypto_market_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesComma-separated list of cryptocurrency ids (e.g. bitcoin,ethereum)
x_paymentNoOptional signed x402 payment payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact — a $0.09 per-call x402 payment cost — but says nothing about data freshness, upstream source, latency, or what happens if payment is omitted, so the added context is thin.

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?

A single compact sentence with no filler. Leading with the price rather than the capability is slightly awkward ordering, but the whole definition is short enough that nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does list the returned fields, which partially compensates. However, it leaves the x402 payment flow unexplained — an agent cannot tell from the text whether the call fails without a signed payload or how to obtain one — which is a meaningful gap for a paid endpoint.

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 description coverage is 100%, with both ids and x_payment documented inline including an example format, so the baseline is 3. The description adds no further meaning about id resolution, batch limits, or when a payment payload must be supplied.

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?

The description names the resource (crypto market metrics) and enumerates the concrete outputs — real-time price, market cap, 24h volume — which lets an agent distinguish it from siblings like perps_mids or defi_yields that cover different data. It is specific but does not explicitly contrast itself with any named alternative.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no routing to alternatives among the many crypto/market siblings. The only implicit cue is that it takes coin ids, so the agent must infer the use case from the name alone.

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