Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WIF

Paid. WIF/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/WIF.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 load and does well: it declares the tool is paid ($0.25 USDC on Base), requires no account or API key, does not charge for failed calls, and names the upstream sources (Coinbase Exchange with a Kraken cross-check). It omits latency, rate limits, and staleness/refresh cadence, which limits it below 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?

Front-loads the billing status, then the payload, then the payment/access terms, then the endpoint — a sensible ordering with almost no filler. The telegraphic fragments ('Paid.', '$0.25 USDC on Base.') are dense but readable; the raw URL is the only element that could be moved out of the prose.

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, no-output-schema tool, the description covers what comes back, what it costs, how payment and access work, and failure charging — enough for an agent to decide and call correctly. A note on response shape (fields vs. prose) or refresh cadence would close the remaining gap.

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 add and the baseline applies. The description correctly implies the symbol is fixed rather than caller-supplied, which prevents an agent from trying to pass a ticker.

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?

States the resource precisely (WIF/USD live price) and enumerates exactly which data points come back: last price, 24h open/high/low, % change, and 24h and 30d volume. Against ~400 buy_coin_* siblings the payload spec plus the explicit pair is enough to identify this tool without opening anything else.

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 by the symbol in the tool name and the description's price payload; there is no statement of when to prefer this over buy_crypto_price or the general crypto tools, and no exclusion for when a WIF-specific quote is not needed. Adequate but leaves routing to the agent.

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