Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RHEA

Paid. RHEA (RHEA) 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/RHEA.

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

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 full burden and does well: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It does not describe the response format or latency, but the pricing and failure policy are substantial behavioral disclosures.

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 description is short and front-loads the critical 'Paid.' warning, followed by data content, payment terms, and endpoint. It is slightly telegraphic and repeats 'RHEA (RHEA)', but every sentence carries useful information.

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 zero-parameter data-fetch tool with no output schema and no annotations, the description covers the essential agent needs: what data is returned, that it costs money, accepted payment chains, that no API key is required, and where the endpoint lives. It is nearly complete, with only minor gaps around the exact response format and payment invocation mechanics.

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 has zero input parameters, so the baseline is 4. The description correctly adds no parameter details because none exist, though it could clarify that invocation requires no arguments beyond the payment mechanism.

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?

The description identifies the specific resource (RHEA token price data) and enumerates the returned data points: live USD price, 24h change, and market-cap rank. It is clearly distinguishable from the hundreds of sibling buy_tok_* tools by ticker, but it lacks an explicit verb like 'returns' or 'fetches' and does not contrast with buy_crypto_price.

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: call this when you need RHEA price data. The payment context ($0.05 USDC on Base or Solana, no account, no API key) is useful, but there is no explicit when-to-use guidance, no exclusions, and no comparison to buy_crypto_price or other alternatives.

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