Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KAIA

Paid. Kaia (KAIA) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/KAIA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose auth (none), cost ($0.01 USDC), and failure handling ('Failed calls not charged'). What it leaves undisclosed is how the payment is actually transacted given zero parameters and no key — the settlement mechanism — as well as any rate limits, caching, or freshness guarantees beyond the word 'live'.

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?

It is densely front-loaded: 'Paid' first, then the payload, then price, then auth, then billing behavior, then the endpoint URL. Every clause carries information, though the telegraphic sentence fragments and raw URL make it read more like a listing than prose.

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, annotation-free tool with no output schema, the description does the essential work: it enumerates the returned fields and states the cost and auth model. The remaining hole — the mechanics of paying with no parameters — is the one thing an agent might still need clarified before invoking.

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 schema has zero parameters, so there is nothing for the description to disambiguate. The baseline for a no-parameter tool applies, and the description correctly spends its words on outputs and cost rather than inventing parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (Kaia / KAIA) and the exact payload returned: live USD price, 24h change, and market-cap rank. An agent can tell what this endpoint produces without inspecting anything else, and the token is unambiguous despite the large sibling namespace.

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 conveys practical context for use — 'Paid', '$0.01 USDC on Base or Solana', 'No account, no API key' — which signals when this is viable. But it never routes against siblings: with buy_crypto_price and the buy_coin_* family present, there is no statement about when this specific per-token paid endpoint should be chosen over those alternatives.

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