Skip to main content
Glama

SouthPow crypto & market data

buy_cp_majors

Paid. Live crypto prices, majors basket (BTC, ETH, SOL): 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/majors.

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

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 cost and accepted payment rails (USDC on Base or Solana), that no authentication is required, that failures are not billed, and the data provenance (median of two named exchanges, each source shown). The remaining gap is how payment is actually transmitted (e.g. a payment header/wallet flow), which is not stated.

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 text is front-loaded ('Paid.' first) and every clause adds decision-relevant information: identity, basket, price, rails, auth, refund policy, endpoint. The telegraphic fragments are efficiently scannable but slightly choppy rather than fully structured prose.

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-param, no-output-schema, no-annotation tool, the description covers the essentials an agent needs: what data comes back and how it is derived, what it costs, what auth is not needed, and where the endpoint is. Only the payment execution mechanics and response shape remain unstated.

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; baseline 4 applies. The description correctly adds no parameter noise.

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 gives a specific resource (live crypto prices) and pins down the exact basket composition (BTC, ETH, SOL) plus the aggregation method (USD median of Coinbase and Kraken). That composition implicitly separates it from siblings like buy_cp_top10 or buy_cp_layer1, though it never names an alternative outright.

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 price ($0.005 USDC), the 'Paid' prefix and 'no account, no API key' tell an agent the cost and prerequisites, and 'failed calls not charged' signals retry is safe. However, there is no explicit when-to-use versus buy_cp_btc-eth, buy_cp_top10, or the per-coin buy_coin_BTC/buy_crypto_price tools, leaving selection to inference from the basket contents.

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