Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BTC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses that the call is paid ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that pricing is cross-checked across two exchanges. What it omits is the practical execution detail an agent needs for a paid call — response shape, latency/freshness of the quoted price, and whether repeat calls within a window are re-charged.

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 the payment flag and the payload contents, then cost, auth, refund policy, and endpoint. It is telegraphic rather than polished prose, but nearly every fragment carries information an agent would otherwise have to discover by trial. Slight deduction for the compressed syntax making the field list read as a run-on.

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?

For a zero-parameter, paid, single-symbol data endpoint with no output schema, the description supplies everything that would otherwise be missing: what fields come back, which exchanges back the numbers, what it costs, how payment is handled, and that failures are free. Little more could be asked of a definition this thin on structured metadata.

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 meaning to convey and the baseline of 4 applies. The description correctly implies the ticker is baked into the endpoint URL rather than being an argument, which prevents an agent from hunting for a symbol input.

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?

Names the specific resource and scope: BTC/USD live price with 24h open/high/low, % change and volume figures, sourced from Coinbase Exchange with a Kraken cross-check. A sibling like buy_coin_ETH is obviously a different asset, so the ticker in the name plus the BTC/USD phrasing separates it cleanly. It stops short of differentiating itself from the generic buy_crypto_price sibling, which appears to overlap in function.

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?

The word 'live' and the enumerated fields imply the use case (current BTC spot snapshot rather than historical or per-asset research), but there is no explicit when-to-use statement and no routing advice toward buy_crypto_price or other price tools. The agent must infer that this is the right pick from the ticker in the name alone.

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