Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KGEN

Paid. KGeN (KGEN) 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/KGEN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose real behavior: $0.01 USDC on Base or Solana, no account or API key required, failed calls not charged, plus the endpoint URL. What it omits is equally important for a paid tool — no statement of rate limits, latency, freshness of the price, or what a failure response looks like. Solid but incomplete for a zero-annotation paid call.

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 clauses, front-loaded with the critical 'Paid.' flag, then the resource, then cost and access terms. No filler, and the most decision-relevant fact (that it costs money) appears first.

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, single-value lookup with no output schema, the description covers what is returned, what it costs, how to pay, and that failures are free — enough to call it correctly. Missing freshness/update cadence for a 'live' price is the only notable gap.

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; the baseline of 4 applies. The description correctly implies no inputs are needed by naming the token inline in the endpoint.

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 resource and what it returns: 'KGeN (KGEN) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back. However, it never distinguishes this from the parallel buy_coin_* family or buy_crypto_price, so sibling differentiation rests entirely on the token symbol in the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no pointer to alternatives such as buy_crypto_price or the buy_coin_* equivalents. The operational notes (cost, chains, no API key) are payment mechanics, not selection guidance, so an agent must infer usage purely from the tool name.

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