Skip to main content
Glama

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

crypto-price

[x402 paid: $0.001 USDC on Base] Live spot crypto price in USD for any pair (BTC, ETH, SOL...), straight from Coinbase. 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": "crypto-price"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairNoexample: BTC-USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious behavior: the call is metered ($0.001 USDC on Base, x402), and 'tools/call returns the live payment challenge' tells the agent the first call will not return a price. It omits what a settled response looks like, retry/idempotency behavior, and any rate limits.

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?

Two sentences, front-loaded with the cost and payment rail before the function, which is the right ordering for a paid tool. Little waste, though 'straight from Coinbase' is decorative and the parenthetical ticker list adds no operational value.

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, no-output-schema tool, the essentials are mostly covered, including the payment prerequisite. However, 'pair' is listed as optional (0 required) with no statement of the default or what happens when omitted, and the description never says what a successful paid response contains.

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 'pair' property already carries an example (BTC-USD), so the baseline is 3. The description adds the idea of 'any pair (BTC, ETH, SOL...)' but its bare-ticker examples differ from the schema's 'BASE-QUOTE' format, which slightly muddies rather than clarifies expected input.

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 and resource: 'Live spot crypto price in USD for any pair', with a named source (Coinbase). It does not distinguish itself from nearby siblings like token-price, usd-price or tool_crypto_price, so an agent cannot tell from the text alone which one 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?

The prepended '[x402 paid: $0.001 USDC on Base]' implies when this tool is worth invoking (only when payment is acceptable), but there is no explicit when-to-use or when-not-to-use guidance versus the many price-adjacent siblings. The agent must infer the trade-off between cost and convenience.

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