Skip to main content
Glama
Sign In

tech-risk

by io.github.rezearcher
OverviewDiscussionsAdmin

crypto_prices

Live spot token prices (price, change_24h, symbol, confidence, timestamp) for CoinGecko ids, sourced from DefiLlama. Cost: $0.005 USDC per call via x402.

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
coinsNoComma-separated ticker symbols or CoinGecko ids, e.g. "ETH,BTC" or "bitcoin,ethereum,solana" (default; max 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / coins / description
      Previous value: -"Comma-separated CoinGecko ids, e.g. \"bitcoin,ethereum,solana\" (default; max 25)"New value: +"Comma-separated ticker symbols or CoinGecko ids, e.g. \"ETH,BTC\" or \"bitcoin,ethereum,solana\" (default; max 25)"
  2. Added

TDQS

A3.8/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 the two things an agent most needs: this is a live/paid call and payment is $0.005 USDC via x402, which implies wallet/auth prerequisites. It does not cover failure behavior (is the charge incurred on error?) or rate limits, which are material for a paid endpoint.

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?

Two sentences, front-loaded with the resource and return fields, then the cost constraint. Every clause carries information; nothing is padding.

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?

No output schema exists, but the description compensates by listing the return fields (price, change_24h, symbol, confidence, timestamp). For a one-parameter, no-annotation tool the only real gap is error/payment-failure behavior and the explicit pointer to the preview sibling.

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 parameter is fully documented there, including comma-separated syntax and the 25-item cap, so the baseline is 3. The description adds little beyond the keying convention ('CoinGecko ids') and is actually slightly narrower than the schema, which also accepts ticker symbols.

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 token prices) and enumerates the returned fields, so the agent knows exactly what comes back. The source (DefiLlama) and CoinGecko-id keying further sharpen it. It stops short of naming the crypto_prices_preview sibling, so differentiation is implied by the cost line rather than stated.

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 cost line ($0.005 USDC per call via x402) implies this is the paid live endpoint and that the free _preview variant exists for sampling, but the description never says so explicitly or gives a when-not condition. The default behavior (top coins, max 25) is only in the schema. Usage is inferable, not guided.

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

All tech-risk toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources