Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KAITO

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

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

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 provided, the description does real work: it discloses the price ($0.05 USDC on Base), that no account or API key is required, that failed calls are not charged, and that Coinbase Exchange is the primary source with a Kraken cross-check. Gaps remain on rate limits, latency, and how the payment is actually transacted, but the commercial and data-provenance 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?

Roughly three dense sentences with no filler, and the most decision-relevant facts (paywalled, live price fields, cost) come first. The telegraphic style and leading fragment "Paid." are slightly cryptic out of context, and the trailing bare URL is less useful than a stated response format.

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 trivial 0-param endpoint with no output schema, the description effectively substitutes for one by enumerating the returned fields, and it covers cost, auth, failure charging, and data provenance. Only minor items (response encoding, rate limits, payment mechanism) are absent.

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 add; baseline for a 0-param schema is 4. The description does not waste space on input semantics, which is correct here.

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?

"KAITO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume" names the exact resource and the exact fields returned, so an agent knows precisely what data comes back. It never uses a verb like fetch/get and never refers to the sibling family (e.g. buy_coin_BTC), so differentiation relies on the coin ticker being embedded in the name and description.

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?

Usage is implied rather than stated: an agent can infer this is the tool for KAITO spot quotes, and "No account, no API key" removes a common prerequisite. There is no explicit when-to-use versus alternatives (e.g. buy_crypto_price for aggregated or multi-asset pricing) and no when-not-to-use guidance.

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