Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WAVES

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 does disclose meaningful behavior: it is paid, costs $0.05 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. What it omits is equally relevant for an agent — there is no indication of rate limits, latency, or freshness/staleness guarantees for 'live' prices, and no statement about payment failure handling.

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?

Roughly three short sentences, front-loaded with the 'Paid.' flag before the purpose, price, and endpoint. Every element — cost, chain, auth posture, failure billing, URL — carries information an agent needs to decide and execute.

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 single-value read with no output schema, the definition covers purpose, cost, payment rails, auth requirements, failure billing, and the backing URL. The remaining gap is response shape and units (e.g., numeric precision or timestamp of the 'live' price), which the description only partially implies through the three listed fields.

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; the token is fixed by the tool name. Baseline 4 applies, and there is no conflicting or missing parameter guidance.

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 states a specific resource and payload: 'Waves (WAVES) price: live USD price, 24h change and market-cap rank.' That is concrete enough to distinguish this tool from unrelated siblings. It does not, however, tell the agent how it differs from the generic buy_crypto_price tool, which is the one substitution an agent would plausibly consider.

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: an agent can infer it should call this when it wants WAVES spot data, and the 'Paid... $0.05 USDC' line signals a cost tradeoff. There is no explicit statement of when to prefer this over buy_crypto_price or of any precondition beyond having USDC on Base or Solana.

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