Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RIO

Paid. Realio Network Token (RIO) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/RIO.

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": "buy_tok_RIO"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 burden well: it discloses that the call is paid at $0.05 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged, plus it gives the endpoint URL. It stops short of describing rate limits, retry behavior, or the exact response shape beyond the three named fields.

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?

Very compact and front-loaded — the paid flag and the data returned come first, then pricing/auth terms, then the URL. The telegraphic style ('Paid.', bare URL) is efficient but slightly terse for an agent needing to parse price terms.

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 parameterless, single-purpose paid quote endpoint with no output schema, the description covers cost, payment rails, auth expectations, failure billing, and returned fields — enough to call it correctly. Only the precise response format and any rate limits remain uncovered.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies the token is fixed by the endpoint rather than supplied as an argument.

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+resource: live USD price, 24h change and market-cap rank for Realio Network Token (RIO). Clear enough to invoke without opening the schema, but it never names or contrasts itself with the many parallel siblings (buy_coin_*, buy_crypto_price, other buy_tok_*), so differentiation is only implicit in the name.

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 context is implied rather than stated: 'Paid' plus the returned fields tells an agent this is a paid quote lookup, and 'No account, no API key' removes a common blocker. There is no explicit when-to-use/when-not guidance nor a pointer to alternatives such as buy_crypto_price or other buy_tok_* endpoints.

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