Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BANANA

Paid. Banana Gun (BANANA) 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/BANANA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/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 so well: it discloses the payment requirement, the exact price and accepted chains, that no auth is needed, and that failed calls are not charged. Those are the non-obvious behaviors an agent needs before a metered call, and they are stated plainly.

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?

The payment caveat is front-loaded with 'Paid.' and each fragment carries distinct information: cost, outputs, auth, refund policy, URL. It is telegraphic rather than polished prose, and the raw URL is slightly wasteful since it is unlikely to need manual entry, but nothing is redundant.

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 paid lookup with no output schema, the description covers cost, payment rails, auth, failure billing, and the returned fields, which is close to everything needed to call it correctly. It does not describe the response shape (units, ordering, JSON structure) or rate limits, which are minor remaining gaps.

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?

There are zero input parameters, so there is no per-parameter meaning to add; the baseline for a parameterless tool applies. The description still contributes by specifying which values come back, but it adds nothing about parameterization because none exists.

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 names a specific resource (Banana Gun / BANANA) and enumerates what it returns: live USD price, 24h change, and market-cap rank. That is far more specific than the name alone. It does not, however, contrast itself with the generic sibling buy_crypto_price or explain why a per-token tool exists, so sibling differentiation is left implicit.

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 states the preconditions for use (paid, $0.01 USDC on Base or Solana, no account, no API key), which tells an agent whether it can call it. It never says when to prefer this over buy_crypto_price or the buy_coin_* family, and there are no explicit exclusions, so usage is only implied.

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