Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WAXL

Paid. WAXL/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/WAXL.

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

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, the description carries the full behavioral burden and does well: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, is not charged on failure, and that data comes from Coinbase Exchange with a Kraken cross-check. It omits rate limits, latency/freshness guarantees, and response format, which keeps it short of a 5.

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?

Dense, front-loaded, and telegraphic: payment status leads, then the data payload, then cost/auth/failure policy, then the endpoint. Every fragment carries information, though the staccato style and the trailing raw URL slightly hurt readability.

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

Completeness5/5

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

For a zero-parameter tool with no output schema and no annotations, the description covers everything an agent needs: what data is returned, the upstream sources, the payment rail and price, the absence of auth, and the failure-charge policy. No material gap remains for a correct invocation decision.

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 no parameter semantics to explain and the baseline is 4. The description correctly adds nothing about inputs and instead spends its words on output fields and commercial terms.

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 exact resource and scope ("WAXL/USD live") and enumerates the returned data points (last price, 24h open/high/low, % change, 24h and 30d volume), so an agent knows precisely what it gets. It does not explicitly contrast itself with the many sibling buy_coin_* tools or with buy_crypto_price, leaving differentiation to the ticker 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?

Usage is implied rather than stated: an agent can infer "call this when you need WAXL's live USD price." The cost ($0.25 USDC on Base) is disclosed, which helps an agent decide whether to pay, but there is no explicit when-not-to-use rule or pointer to the cheaper/alternative price tools among the siblings.

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