Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PRO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rail, that no account or API key is needed, and that failed calls are not charged. It also names the upstream data sources (Coinbase Exchange with Kraken cross-check), which matters for trust. Gaps remain on rate limits, latency, and payment mechanics (e.g. how the $0.01 is settled per call).

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-loaded with 'Paid.' — the single most decision-relevant fact — followed by data contents, then cost/auth, then the URL. The telegraphic fragment style packs a lot into three lines with no filler. It loses a point only because the fragments are dense enough to require a second read.

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-annotation, no-output-schema tool, the description covers the essentials: what data comes back, what it costs, that no credentials are needed, and the endpoint. It effectively substitutes for a missing output schema by listing the returned fields. It stops short of stating the response format or whether the URL is a direct x402-style HTTP endpoint an agent could call itself.

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 of 4 applies. The description correctly implies no inputs are needed by supplying the symbol and endpoint URL directly.

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 a specific resource and pair (PRO/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. That is far more specific than the bare name, though it never explicitly frames itself against the many buy_coin_<SYMBOL> siblings or the generic buy_crypto_price tool, leaving symbol-based differentiation to the name alone.

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?

Cost and access conditions ('$0.01 USDC on Base', 'No account, no API key', 'Failed calls not charged') tell an agent what it is committing to, which implicitly gates usage. However, there is no explicit when-to-use versus alternatives guidance, e.g. no routing to buy_crypto_price for a generic quote or any note on when a free source would suffice.

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