Skip to main content
Glama

SouthPow crypto & market data

buy_cp_payments

Paid. Live crypto prices, payments basket (XRP, XLM, LTC, BCH, DASH): 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/payments.

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

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?

With no annotations, the description carries the full burden and does well: it discloses the paid nature, exact cost ($0.005 USDC), accepted chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing the response payload structure beyond 'each source shown'.

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-loads the paid flag, then coverage, methodology, price, and access terms in short clauses with no filler. The trailing raw URL is slightly awkward but functional.

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-argument tool with no annotations and no output schema, the description covers cost, payment rails, access requirements, billing failure behavior, and data provenance (median of two named exchanges). The only real gap is the shape of the returned data.

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 no parameter meaning to convey and the baseline of 4 applies. The description correctly does not waste space on arguments.

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?

States the concrete resource: a crypto price basket covering XRP, XLM, LTC, BCH and DASH, computed as a USD median of Coinbase and Kraken. Naming the exact coin set distinguishes it from sibling baskets like buy_cp_majors or buy_cp_top10, though the leading verb 'buy' is never explained as a purchase action.

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?

The coin coverage implies when this basket is preferable to single-coin tools such as buy_coin_XRP or buy_coin_LTC, but no alternative is named and no when-not condition is given. An agent must infer routing from the ticker list alone.

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