Skip to main content
Glama

SouthPow crypto & market data

buy_tok_REUR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it discloses genuinely useful behavior: paid ($0.01 USDC on Base or Solana), no account/API key required, and failed calls are not charged. It omits freshness/polling expectations, rate limits, and what a 'failed' call looks like (HTTP error vs. empty payload), which matters for a paid endpoint an agent may retry.

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?

Six short fragments, front-loaded with cost and payload, then payment mechanics, then the endpoint URL. Dense and largely waste-free, though the bare URL is presented without explanation of when an agent would need it over the tool itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter paid lookup with no output schema, the description covers cost, payment rails, failure charging, and the three returned fields — most of what is needed. It stops short of describing response shape or error behavior, which is the remaining gap given no annotations or output schema back it up.

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 the baseline is 4; the description correctly stays silent on inputs and does not invent parameters that the empty schema would contradict. Nothing is lost by the schema handling this alone.

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 the specific asset (Royal Euro / REUR) and exactly what is returned: live USD price, 24h change, and market-cap rank. The token symbol in the name plus the REUR mention in the description differentiates it from other per-asset siblings, though it never says how it differs from generic tools like buy_crypto_price or from the buy_coin_* family.

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 only implied — the presence of a price and a cost tells the agent this is a paid single-asset quote, but there is no explicit 'use this when you need X' or a named alternative for multi-asset or historical lookups. The agent must infer the selection rule from the tool name alone.

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