Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CLANKER

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

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

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 reasonably well: it discloses that the call is paid ($0.05 USDC on Base), the payment currency and chain, that no auth is needed, and that failures are not charged. It doesn't cover rate limits, latency, or what a failure looks like, but the commercial and access behavior is unusually well surfaced.

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 'Paid.' and then packs fields, sources, price, access terms and URL into three compact sentences with no filler. The telegraphic style is dense but readable; a slightly clearer separation of what is returned vs what is charged would help marginally.

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?

No output schema and no annotations exist, so the description must enumerate returns and access terms itself — it does both, listing the exact metrics and the price/payment details. Missing only edge behavior such as staleness or error formats, which is a minor gap for a single-pair price lookup.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on cost and data sources, which is the right allocation for a no-arg tool.

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 a specific resource and dataset: CLANKER/USD last price, 24h OHLC, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). The one ambiguity is that the 'buy_' name prefix suggests purchasing something, while the description makes clear this is a price-data call; the description corrects that, but doesn't explicitly say how it differs from generic siblings like buy_crypto_price.

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 useful preconditions (no account, no API key, failed calls not charged) and the exact endpoint, which tells an agent this is callable immediately. However, it never says when to choose this over buy_crypto_price or another pair endpoint, and no exclusions or alternatives are named.

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