Skip to main content
Glama

YRUZ Crypto Price (0.002 USDC)

crypto_price
Read-onlyIdempotent

Live prices in one fast call for up to 25 assets: any coin by CoinGecko id or ticker symbol (btc, eth, sol, usdc...) and any Solana token by mint address. Returns price, 24h change, 24h high/low, market cap, volume, rank and the source, in USD or another currency. Cached at most 60 s; Binance and Jupiter as fallbacks. Price: 0.002 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"crypto_price"}. Same tool over HTTP: https://yruz.one/api/crypto/price?ids=bitcoin%2Cethereum%2Csolana

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

Input Schema

NameRequiredDescriptionDefault
vsNoquote currency, default usd (eur, gbp, jpy, btc, eth ...)
idsYescomma-separated coins or mints (required), e.g. btc,eth,sol or a Solana mint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ids / examples
      Added value: +[
      +  "bitcoin,ethereum,solana"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations: discloses 60-second caching, Binance and Jupiter fallback sources, the 0.002 USDC x402 payment requirement with no account or API key, that invalid input is rejected before charging, and that failed runs are never billed. It also states the failure mode without payment (x402 PaymentRequired), which is exactly the kind of behavior an agent must anticipate before invoking.

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 capability and return payload before the payment mechanics, and nearly every sentence carries operational weight. It is a dense run-on paragraph, and the trailing HTTP URL example is the weakest line for an agent that already has an MCP tool, but nothing is seriously padded.

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?

For a two-parameter read-only tool with no output schema, the description fully specifies the return shape (price, 24h change, high/low, market cap, volume, rank, source), the currency dimension, freshness limits, and the payment failure path. An agent can call this correctly and interpret the result without further information.

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, and the description adds real meaning on top: the batch ceiling of 25 assets, that ids accepts either a CoinGecko id or a ticker symbol, and that vs supports non-USD quote currencies including crypto. No syntax examples for mint addresses beyond the schema example, keeping it at 4 rather than 5.

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 price lookup for up to 25 assets, accepting CoinGecko ids, ticker symbols, or Solana mint addresses, with the returned fields enumerated. It is clear what the tool does, but it never names the adjacent siblings it could be confused with (crypto_trending, solana_token_check), so an agent still has to infer the boundary.

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?

Provides concrete operational guidance on calling it (get_example {"tool":"crypto_price"}) and an equivalent HTTP endpoint, and explains the payment precondition. However, it gives no when-to-use/when-not-to-use guidance relative to siblings like crypto_trending or solana_token_check, leaving the selection decision to inference.

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.