Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BURN

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

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

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?

No annotations are supplied, so the description carries the full burden and it does so well: it discloses that the call is paid ($0.01 USDC), the accepted payment chains (Base or Solana), that no auth or API key is needed, and that failed calls are not charged — the key risk facts for a paid endpoint. It omits return format (JSON vs. otherwise), latency, and any rate limits.

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?

One dense sentence that is front-loaded with the most important qualifier ('Paid') and then packs in payload, cost, chains, auth and billing-failure policy without filler. The trailing raw URL is slightly mechanical but still earns its place as the underlying endpoint.

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-purpose paid lookup with no output schema and no annotations, the description covers the decisions an agent must make: whether to pay, how to pay, whether credentials are needed, and what a failure costs. The main remaining gap is the lack of differentiation from the sibling token-price tools.

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 and the input schema is an empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies; the URL is offered as supplementary context rather than as a parameter explanation.

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 states a specific verb+resource+payload: it returns the BurnedFi (BURN) live USD price, 24h change and market-cap rank. That is precise enough to know exactly what comes back. It does not, however, distinguish itself from the near-identical sibling buy_coin_BURN or from the generic buy_crypto_price, so the agent gets no explicit routing cue.

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 context is implied rather than stated: the 'Paid' prefix and the '$0.01 USDC on Base or Solana' clause tell the agent this costs money, and 'No account, no API key' removes a prerequisite. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the overlapping buy_coin_BURN sibling, which is the most likely mis-selection in this catalogue.

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