Skip to main content
Glama

crypto_prices

Fetch spot cryptocurrency prices for comma-separated CoinGecko IDs in a chosen quote currency; calls are paid per use via x402, with free quotes when no wallet is configured.

Instructions

Get spot prices for comma-separated CoinGecko ids (default ripple,ripple-usd) in a quote currency (default usd). Price about $0.002. Paid per call with x402 from your XRPL_SEED wallet (XRP or RLUSD, capped by MAX_*PER_CALL and SESSION_BUDGET*). Without a wallet it returns the price quote and charges nothing. Failed calls are not charged.

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_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
vsNoQuote currency, e.g. usd
idsNoComma-separated CoinGecko ids
assetNoAsset to pay with on the XRP Ledger: XRP (default) or RLUSD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so well: it discloses that each call is paid via x402 from an XRPL_SEED wallet, that payment can be XRP or RLUSD, that spend is bounded by MAX_*_PER_CALL and SESSION_BUDGET_* caps, that a wallet-less call returns a quote with no charge, and that failed calls are free. These are exactly the behavioral facts an agent needs before committing to a paid call.

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?

Front-loads the core capability and defaults, then adds payment and failure semantics in tight sentences with no filler. It is dense with environment-variable names, which costs some readability, but nothing is redundant.

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 3-optional-parameter tool with no annotations and no output schema, the description covers cost, authorization, spend limits, fallback behavior, and failure charging. The only real gap is the shape of the returned price payload, though 'returns the price quote' gives a rough signal.

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 already 100%, so the baseline is 3; the description earns above that by supplying default values ('ripple,ripple-usd' for ids, 'usd' for vs) that the schema does not declare, which materially affects what a zero-argument call returns. The 'asset' enum and its XRP default are already in the schema, so that portion adds nothing new.

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?

Opens with a specific verb and resource ('Get spot prices') and pins down the exact domain (CoinGecko ids) and unit (quote currency). The example ids and defaults make it unambiguous what the tool returns, and it is clearly distinguishable from siblings like web_to_markdown or xrpl_account_info.

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 implied rather than stated: the reader learns the defaults and that it works without a wallet, but there is no explicit 'use this when...' or exclusion against related tools such as call_paid_service. The no-wallet fallback is effectively a usage precondition, which is helpful, but the agent must infer when to prefer this tool over a generic paid-call tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.