Skip to main content
Glama

SouthPow crypto & market data

buy_cp_gaming

Paid. Live crypto prices, gaming basket (IMX, SAND, MANA, AXS, GALA, APE, ENJ): USD median of Coinbase and Kraken, each source shown. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/gaming.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description does substantial work: it discloses that the call is paid ($0.005 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that prices are a median of two named exchanges with each source surfaced. It stops short of describing response shape or freshness/latency guarantees beyond the word 'Live'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Telegraphic and front-loaded: payment status first, then data content and sourcing, then price and rails, then operational guarantees, then the URL. No sentence is redundant, and nothing important is buried.

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, this covers the essentials an agent needs: what data, from which sources, at what cost, on which rails, and with no auth. The one gap is that with no output schema the description could sketch the response structure (e.g., per-coin entry with per-source fields) rather than leaving it to inference.

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 and the baseline of 4 applies. It correctly implies no configuration is needed by stating 'No account, no API key'.

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?

The description names the exact resource (live crypto prices for a gaming basket) and enumerates every constituent ticker (IMX, SAND, MANA, AXS, GALA, APE, ENJ), which unambiguously separates it from the hundreds of buy_coin_* siblings and the other buy_cp_* category baskets. The aggregation method (USD median of Coinbase and Kraken) is stated too, so an agent knows exactly what it gets before calling.

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 implied by the coin list and the 'Paid' framing, but the description never says when to prefer this basket over individual buy_coin_IMX/buy_coin_SAND calls or over buy_crypto_price, nor when not to use it. The cost and payment mechanics give useful selection context, but there is no explicit alternative routing.

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