Skip to main content
Glama

YRUZ Crypto Trending (0.003 USDC)

crypto_trending
Read-onlyIdempotent

What the crypto market is doing right now: the most searched coins, the top 24h gainers and losers among the 250 largest coins, global market cap and BTC dominance, and the trending Solana tokens of the last hour with price, liquidity and organic volume. Price: 0.003 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_trending"}. Same tool over HTTP: https://yruz.one/api/crypto/trending?limit=10

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

Input Schema

NameRequiredDescriptionDefault
limitNoitems per list, 1-20 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / examples
      Added value: +[
      +  "10"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description discloses the critical behavior an agent cannot get from structured fields: 0.003 USDC per call via x402, no account or API key, invalid input refused before payment, failed runs never charged, and PaymentRequired returned without payment. That is precisely the payment/auth and failure-mode context that matters for an agent deciding whether to 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?

The payload description is front-loaded and dense with concrete nouns, with payment mechanics following. It is somewhat long, and the HTTP-endpoint line plus the get_example pointer are operational boilerplate, but both are genuinely useful for invocation and neither is filler.

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?

There is no output schema, so the description must carry the return contract, and it does: it enumerates each data block returned. Combined with payment semantics, the failure path, and the invocation pointer, an agent has everything needed to call it correctly and interpret the result.

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 `limit` parameter is already documented as 'items per list, 1-20 (default 10)', so the schema does the work. The description only echoes the default via the `?limit=10` URL example and does not clarify that the limit applies per list rather than to the total result set. Baseline 3 is appropriate.

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?

The description names a specific resource (current crypto market state) and enumerates exactly what it returns: most searched coins, top 24h gainers/losers among the 250 largest coins, global market cap and BTC dominance, and trending Solana tokens with price/liquidity/organic volume. That scope is clearly distinguishable from siblings like crypto_price (single price) and solana_token_check (single token audit).

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 by 'what the crypto market is doing right now' and the enumerated payload, so an agent can infer this is a market-overview call rather than a single-asset lookup. However, it never explicitly contrasts itself with crypto_price, solana_token_check, or yruz_list_services, and there are no stated exclusions or preconditions for choosing this tool.

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.