Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

usd-price

[x402 paid: $0.001 USDC on Base] Batch crypto prices: up to 10 pairs in one request — one call instead of ten. tools/call returns the live payment challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "usd-price"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairsNoexample: BTC,ETH,SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 disclose two non-obvious behaviors: the tool is metered at $0.001 USDC on Base via x402, and tools/call returns a live payment challenge the agent must handle. It omits failure modes, what happens when more than 10 pairs are supplied, and the response shape.

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?

Three compact clauses: payment cost first, then the batching benefit, then the payment-challenge behavior. Nothing is padded and the most decision-relevant facts are front-loaded.

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?

For a one-parameter tool this covers cost, batching, and the payment handshake, but with no output schema the description should say what a successful result looks like (price fields, quote currency, handling of unknown pairs). That gap matters for an agent that must parse the response.

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 'pairs' parameter is already documented with an example (BTC,ETH,SOL). The description adds the 10-pair cap, which the schema does not state, but gives no delimiter or formatting detail beyond that baseline.

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 concrete capability: batch crypto prices for up to 10 pairs in a single request. That is specific enough for an agent to know what it gets, though the name 'usd-price' suggests a single-price lookup and the description never says the prices are quoted in USD, leaving a small mismatch an agent must resolve.

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?

'One call instead of ten' implies the batching use case and a 10-pair ceiling, which is useful guidance. It stops short of naming when to prefer a single-pair sibling such as crypto-price or token-price, and there are no explicit exclusions or prerequisites.

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