Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KAT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rail, that no credentials are required, and that failed calls are not charged. It also names the data sources (Coinbase Exchange with Kraken cross-check). What's missing is any statement about rate limits, latency, or whether the payment is per-call or per-session.

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?

The description is front-loaded with 'Paid.' followed immediately by the payload, then commercial terms, then the raw URL. Every clause carries information; nothing is padding. The telegraphic style (fragments, colon lists) is dense but readable.

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-param, no-annotation, no-output-schema price fetch, the definition covers what an agent needs to decide and call: what data comes back, what it costs, how to pay, and that no auth exists. The only gap is that the response's shape and units (e.g. whether % change is a fraction or percent) are not spelled out and no output schema compensates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which normally sets a baseline of 4. The description adds no parameter information because there is nothing to parameterize — the coin, quote currency, and endpoint are all baked in. It is adequate but adds nothing on this axis.

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 verb-less but unambiguous resource: live KAT/USD data with an enumerated payload (last price, 24h open/high/low, % change, 24h and 30d volume). The coin symbol in the name plus the explicit 'KAT/USD' in the text makes it distinguishable from the ~300 sibling buy_coin_* tools, though it never points at buy_crypto_price as the general-purpose alternative.

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?

It states the commercial conditions (paid, $0.25 USDC on Base, no account, no API key, failures not charged), which is genuinely useful context for deciding whether to call. However, there is no guidance on when to prefer this over buy_crypto_price or other price siblings, and no exclusions. Usage is implied by the tool name rather than stated.

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