Skip to main content
Glama

SouthPow crypto & market data

buy_coin_W

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

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

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?

No annotations exist, so the description carries the full behavioral burden and does well on the commercial side: it discloses the $0.05 USDC-on-Base charge, the no-auth requirement, and — valuably — that failed calls are not billed. It stops short on rate limits, latency, and what a failure looks like (no output schema exists to cover the return shape), which are the remaining gaps for an unannotated paid endpoint.

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?

Extremely economical — every clause carries a distinct fact (cost, payload, sources, auth, billing policy, endpoint). The telegraphic fragment style ('Paid.' / 'No account, no API key.') is efficient and front-loads the cost, though the abrupt fragments read more like an ad than prose and slightly reduce scannability.

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?

Given zero parameters, no annotations, and no output schema, the description supplies exactly the missing pieces: the returned fields are enumerated, the sources are named, the payment and failure policy are stated, and the raw URL is given. An agent has everything needed to decide to call and to interpret what comes back.

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, which is the baseline-4 case; the asset and data set are fixed by the endpoint. There is nothing for the description to disambiguate, and it appropriately does not waste words on nonexistent 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?

States the resource precisely — W/USD live price plus the exact fields returned (last, 24h open/high/low, % change, 24h and 30d volume) and the upstream sources. What's missing is an explicit verb; 'Paid. W/USD live:' leaves the agent to infer that this is a fetch/purchase call rather than something else. Differentiation from siblings rests entirely on the ticker in the name rather than on anything in the description.

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?

Gives practical framing for when the call is appropriate (paid, no account, no API key needed, failed calls not charged), which helps an agent decide to try it. However, it never states when to use this instead of the general sibling buy_crypto_price, nor does it set expectations about repeated/parallel calls or budget discipline. Usage is implied by the ticker, not explained.

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