Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN5

Paid. OpenKaito (SN5) 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/SN5.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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, the exact price and accepted chains, that no auth is needed, and that failed calls are not charged — the billing risk profile an agent needs before spending. It omits response shape, latency, and any rate limits or per-call caps.

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?

Very short and front-loaded: name, payload, price, access terms, billing guarantee, endpoint. The telegraphic fragment style ('Paid.', '$0.05 USDC on Base or Solana.') is dense rather than wasteful, though the URL is low-value for an agent that cannot call it directly.

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 parameterless, single-purpose paid endpoint with no output schema, the description supplies what actually matters: what data comes back, what it costs, how to pay, and that failures are free. Return field names and format are the only meaningful gap, and that is a minor one here.

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 has zero parameters, so there is nothing to disambiguate and the baseline applies. The description adds the useful implicit context that the token is fixed by the tool itself rather than passed in.

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?

States a specific verb-and-resource ('OpenKaito (SN5) price') plus the exact payload contents: live USD price, 24h change, market-cap rank. The token identifier SN5/OpenKaito distinguishes it from the hundreds of sibling buy_tok_* endpoints without opening any schema.

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?

The description implies when to use it (you need SN5 pricing) and states access conditions — no account, no API key, $0.05 USDC on Base or Solana. It does not name any alternative (e.g., a generic crypto-price endpoint or the buy_coin_* family) or say when this is the wrong choice, so routing relies on the agent inferring from the token symbol.

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