Skip to main content
Glama

SouthPow crypto & market data

buy_coin_A8

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 does so well: it discloses cost ($0.10 USDC on Base), that no account or API key is required, that failed calls are not charged, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. Gaps remain around rate limits, latency/staleness, and response format, which keeps it from 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?

Every fragment carries information and the paid/cost constraint is placed first, which is the right priority for a metered endpoint. The telegraphic style ('Paid.', '$0.10 USDC on Base.') reads as shorthand rather than prose, which slightly hurts scanability but wastes no words.

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 price fetch with no output schema, the definition covers the things an agent actually needs before calling: cost, payment rail, auth requirements, failure billing, and the payload fields. The main omission is any indication of the response structure or freshness of the quotes.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the asset is fixed by the tool itself rather than supplied at call time.

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 and quote currency (A8/USD) and enumerates the exact data returned: last price, 24h open/high/low, % change, 24h and 30d volume. That is enough to distinguish it from the hundreds of sibling buy_coin_* tools, which differ only by ticker. It loses a point because no verb frames the operation (it opens with 'Paid.'), so the agent must infer 'fetches price data' from the field list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this versus buy_crypto_price or any other price-oriented sibling, and no when-not guidance. The only usable routing signal is the ticker in the tool name plus the 'Paid.' prefix, which implies a paid alternative to free tools without saying so.

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