Skip to main content
Glama

SouthPow crypto & market data

buy_crypto_price

Paid. Live crypto spot prices in USD for up to 10 coins per call (BTC, ETH, SOL ...), median of Coinbase and Kraken with each source shown. $0.05 USDC on Base. No account, no API key. URL https://southpow.media/v1/crypto-price.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>"
    },
    "name": "buy_crypto_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesComma-separated symbols, e.g. BTC,ETH,SOL

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 that the tool is paid ($0.05 USDC on Base), requires no account or API key, and that prices are a median of two named sources with both shown. Gaps remain around what happens for unsupported symbols, the 10-coin limit breach, and whether the charge applies per call or per symbol.

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?

Four short sentences, front-loaded with the payment flag and the core capability, then price/source detail, then cost and auth, then the endpoint. No filler; each clause carries a fact the agent needs.

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 paid, single-parameter read tool with no output schema and no annotations, the description covers cost, auth, sources, aggregation method, and a call-size limit – enough to call it correctly and predict the rough response shape ('each source shown'). Only edge-case behavior (invalid symbols, over-limit batches, payment failure) is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single 'symbols' parameter, so the format ('Comma-separated symbols, e.g. BTC,ETH,SOL') is already fully documented. The description adds one meaningful constraint not in the schema – a maximum of 10 coins per call – but nothing else about symbol validity or casing. With only one parameter, this is a modest but real addition over the schema baseline.

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 a specific verb and resource ('Live crypto spot prices in USD') and pins down the scope ('up to 10 coins per call', 'median of Coinbase and Kraken with each source shown'). It does not name or contrast any sibling (e.g. the single-coin buy_coin_* tools), so an agent must infer the batch-vs-single distinction from the coin limit alone.

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 scope statement – call this when you need USD spot prices for one to ten symbols from two exchanges. There is no explicit when-to-use/when-not guidance and no named alternative for single-coin or non-USD price needs, leaving the agent to infer routing from sibling names.

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