Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GAMA

Paid. Gama Token (GAMA) 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/GAMA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 disclose meaningful behavior: it is a paid call, the price and accepted chains/payment, that no auth is required, and that failed calls are not charged. It does not cover rate limits, latency, or what a partial/failed response looks like 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?

Front-loaded with 'Paid.' then the data returned, then cost/access terms, then the endpoint URL. Every clause is informative, though the raw URL is of marginal use to an agent and adds a little clutter.

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, no-output-schema tool the description covers what is returned, the cost, the payment rails, and the no-auth and no-charge-on-failure guarantees, which is enough to call it correctly. Output formatting details are the only notable omission, and no output schema exists to cover them.

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 schema is trivially complete. Baseline 4 applies for a no-parameter tool.

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 the specific resource and verb-equivalent operation (GAMA token live USD price, 24h change, market-cap rank), so an agent knows exactly what data it returns. It does not explicitly contrast itself with the many buy_coin_*/buy_tok_* siblings, relying on the token symbol in the name to differentiate.

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 by the token-specific content and the payment terms ('$0.05 USDC on Base or Solana. No account, no API key'), which tell an agent what it costs and what prerequisites are unnecessary. There is no explicit when-to-use vs an alternative (e.g. buy_crypto_price or buy_coin_*) and no stated exclusions.

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