Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KUB

Paid. KUB Coin (KUB) 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/KUB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavioral burden, and it does disclose several operationally important facts that structured fields do not: the call is paid ($0.01 USDC on Base or Solana), needs no account or API key, and failed calls are not charged. Gaps remain around latency/freshness, rate limits, and the exact response shape, which matter for an agent deciding whether to invoke it before showing data to a user.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the 'Paid.' signal, then the payload, then price/chain, then reliability terms, then the endpoint URL. Every element is functional and nothing is restated from the schema or name.

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?

This is a trivial zero-parameter tool with no output schema, so the description must convey what comes back — and it lists price, 24h change, and market-cap rank. Payment terms and failure policy are also covered. Only finer detail such as response format or update cadence is missing, which is minor at this complexity.

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 input schema has zero properties, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly implies no inputs are needed by embedding the token symbol in the tool itself.

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 resource and payload: 'KUB Coin (KUB) price: live USD price, 24h change and market-cap rank.' That is a clear verb-plus-resource statement an agent can match to a token. It does not, however, distinguish this from the hundreds of sibling buy_tok_* tools or from generic tools like buy_crypto_price, so an agent must infer the per-token convention.

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 only implied: the name and description make plain this returns KUB pricing. There is no explicit when-to-use versus when-not, and no pointer to buy_crypto_price or another sibling as the alternative for a different asset. The payment and no-account notes give context but are not routing 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