Skip to main content
Glama

SouthPow crypto & market data

buy_tok_A7A5

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

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

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 load and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged — all non-obvious traits an agent needs before invoking a paid endpoint. It stops short of describing latency, rate limits, or the shape/field names of the response, which leaves some behavioral gaps.

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?

Compact and mostly front-loaded, with cost and payment terms stated first and the endpoint URL last. There is minor waste in the redundant "A7A5 (A7A5)" repetition and the one-word "Paid." sentence, but nothing is padded.

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 paid price lookup with no output schema, the description covers what is returned, what it costs, which chains settle payment, and the failure-charge policy — enough to call it correctly. The remaining gap is that response field names and structure are unspecified, so an agent cannot plan parsing ahead of the call.

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 the token is baked into the endpoint rather than passed in, matching the empty schema.

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?

"A7A5 (A7A5) price: live USD price, 24h change and market-cap rank" names the exact resource and the three specific data points returned, so an agent knows precisely what it gets without opening anything else. Combined with the token-specific tool name, it is distinguishable from the hundreds of buy_tok_* and buy_coin_* siblings by identity.

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 only implied: an agent can infer this is the tool to call when it needs the current A7A5 price. There is no explicit guidance on when to prefer this over buy_coin_A7A5 or buy_crypto_price, nor any stated exclusion, which matters given the very dense sibling set.

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