Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KII

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

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

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, the description carries the full burden and does well: it discloses cost ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency, and caching/freshness guarantees, which is the remaining gap for a paid endpoint.

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 short sentences, front-loaded with the fact that the call is paid, then the payload, then the terms and endpoint. Telegraphic phrasing keeps it compact; nothing is redundant, though the sentence fragments read more like ad copy than spec text.

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, no-output-schema tool, the description supplies what the response contains, the cost, the payment rails, and the failure-charging policy. An agent can decide and invoke correctly; only freshness and rate-limit behavior are unstated.

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 nothing for the description to disambiguate; baseline is 4. The description correctly implies the token is fixed by the tool rather than passed as an argument, which prevents an agent from hunting for a symbol parameter.

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 verb and resource (buy KII price) and enumerates the returned fields: live USD price, 24h change, market-cap rank. It does not name a sibling such as buy_crypto_price or buy_coin_* to explain why this token-specific entry exists, so differentiation is left to the tool name rather than the prose.

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 by the name and the 'Paid' prefix, and the price/payment terms imply this is a per-call purchase. There is no explicit statement of when to prefer this over buy_crypto_price or a buy_coin_* sibling, and no guidance on when the call is unnecessary.

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