Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WAXP

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses that the call is paid, the exact cost and accepted chains, that no credentials are needed, and that failed calls are not billed — important for an agent deciding whether to spend. It stops short of describing rate limits, data freshness/latency, or response shape.

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?

It is a handful of short clauses, front-loaded with 'Paid.' and the data payload, with cost and endpoint following. Every sentence adds a fact an agent needs (what, price, auth, billing behaviour, URL) and none is filler.

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 paid endpoint with no output schema and no annotations, the definition covers the essentials: what is returned, what it costs, how to pay, and the endpoint. The main remaining gap is the response format and any freshness/staleness guarantees, which nothing else in the structured data supplies.

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 and the schema is empty, so there is no per-argument semantics to explain and the baseline of 4 applies. The description correctly adds nothing spurious about inputs.

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 names the specific asset (WAX/WAXP) and the exact payload (live USD price, 24h change, market-cap rank), so an agent knows precisely what data it is buying. It does not explicitly contrast itself with near-neighbours such as buy_crypto_price or buy_coin_WAXL, leaving sibling routing to the token suffix in the tool 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?

Payment terms ($0.05 USDC on Base or Solana, no account or API key required, no charge on failures) give useful preconditions for calling it. However there is no explicit statement of when to prefer this over buy_crypto_price or other tok_ endpoints, so the alternative-selection guidance is only implied.

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