Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WLD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 largely meets it: it discloses the cost ($0.002 USDC on Base), the payment model, that no account or API key is needed, that failed calls are not charged, and the underlying data sources. It stops short of rate limits, latency, or refresh cadence, which matter for a paid live-price feed.

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?

Extremely compact: lead with 'Paid.', then the payload contract, then cost/access terms, then the endpoint. Every clause carries distinct information, and the cost and charge-failure caveats are front-loaded rather than buried.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their sources, so an agent knows what a successful call yields. For a single-purpose, zero-parameter paid endpoint this is nearly sufficient; only response format (JSON envelope, error shape) is unstated.

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 no parameters (empty object schema, 100% coverage), so there is nothing for the description to clarify about inputs; baseline is 4. The URL line usefully pins the endpoint per asset, though it is redundant with the tool identity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact pair (WLD/USD live) and enumerates what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, plus the upstream sources (Coinbase Exchange with Kraken cross-check). Combined with the ticker-bearing tool name, an agent can tell this apart from the hundreds of sibling buy_coin_<TICKER> tools without opening any schema.

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?

It implicitly defines the usage context (a paid, keyless price feed) and states that failed calls are not charged, which informs a risk decision. But it never says when to prefer this over buy_crypto_price or buy_search, nor when not to call it; usage is left implied by the ticker in the name.

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