Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CYBER

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact cost and accepted chains, that no account or API key is needed, and that failed calls are not charged. That is genuine behavioral context. It stops short of describing rate limits, response latency, or failure modes beyond the no-charge guarantee.

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?

Dense, front-loaded telegraphic style that leads with 'Paid.' and then the payload, cost, auth, and failure terms, ending with the endpoint. Minor redundancy in 'CYBER (CYBER)' and no wasted clauses.

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-param paid lookup with no output schema, the description covers the returned fields, cost, payment chains, auth requirements, and failure charging policy. That is close to everything an agent needs to decide and call correctly; only granular response shape is unspecified, which is acceptable 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 takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter confusion is possible.

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 payload: 'CYBER (CYBER) price: live USD price, 24h change and market-cap rank.' An agent immediately knows what data comes back. It does not, however, differentiate itself from the comparable buy_coin_* / buy_crypto_price siblings or explain why a per-token tool exists.

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?

It signals this is a paid call and names the payment rails (Base or Solana) plus the price ($0.01 USDC), which implicitly tells the agent the precondition for invoking it. There is no explicit when-to-use or when-not guidance relative to the many near-identical price siblings.

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