Skip to main content
Glama

SouthPow crypto & market data

buy_cp_btc-eth

Paid. Live crypto prices, btc eth basket (BTC, ETH): USD median of Coinbase and Kraken, each source shown. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/btc-eth.

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_btc-eth"
  }
}

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 to lean on, the description carries the burden well: it discloses the payment amount and rails, that no auth is needed, that failed calls are not charged, and the underlying data sources and aggregation method. It does not state price freshness/update cadence or what a failure response looks like, but the core behavioral profile is unusually complete.

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?

Information is front-loaded in a sensible order: paid flag, what is returned, price and payment rails, auth, failure policy, endpoint. The telegraphic phrasing ('btc eth basket (BTC, ETH)') is slightly redundant, but nearly every clause carries decision-relevant content.

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?

With no output schema and no annotations, the description still explains the return composition (median plus per-source values) and the commercial/access terms. The remaining gap is freshness/latency and the shape of the paid response envelope, which an agent would want before committing $0.01.

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 baseline of 4 applies. The description's explanation of what is fixed (the BTC/ETH pair and the two sources) is a useful substitute for parameter choice.

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 exact resource and computation: a BTC+ETH basket returning the USD median of Coinbase and Kraken with each source shown. That is enough to distinguish it from single-coin siblings like buy_coin_BTC or buy_coin_ETH, though it never names an alternative explicitly.

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?

Operational context is clear (paid, $0.01 USDC on Base or Solana, no account or API key required, failed calls not charged), which tells an agent what it takes to call it. However, there is no guidance on when to pick this basket over buy_crypto_price, buy_coin_BTC plus buy_coin_ETH, or buy_cp_majors, so the selection decision is left 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