Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KEKIUS

Paid. Kekius Maximus (KEKIUS) 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/KEKIUS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and what fields come back. That covers cost, auth, and failure economics. It stops short of rate limits, latency, or what constitutes a 'failed' call, which keeps it from a 5.

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?

Five short fragments, each carrying a distinct fact: price concept, returned fields, cost, payment rails, auth, failure policy, endpoint. Nothing repeats what the schema already says, and the cost/payment facts are front-loaded where an agent will see them before committing.

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 price lookup, the description supplies everything needed to decide and call: the payload, the price, the payment rails, and the failure policy. The only real gap is the payment mechanics — how the x402/USDC charge is actually transacted at call time — which an agent may still have to discover.

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 the baseline is 4 and there is no parameter meaning to add. The description correctly implies the token is fixed by the endpoint rather than passed in, which prevents an agent from hunting for a missing symbol argument.

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?

Names a specific resource (Kekius Maximus / KEKIUS) and the exact payload it returns: live USD price, 24h change, market-cap rank. That is a clear verb+resource result. It does not, however, distinguish itself from the generic sibling buy_crypto_price or explain what a per-token buy_tok_* endpoint gives that the generic one does not.

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 token-specific name and the 'live USD price' framing, but there is no explicit when-to-use guidance and no named alternative such as buy_crypto_price or buy_coin_KEKIUS-style aggregates. The 'Paid. ... $0.01 USDC' note gives the agent a cost gate to weigh, which is a partial routing signal.

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