Skip to main content
Glama

SouthPow crypto & market data

buy_cp_top10

Paid. Live crypto prices, top10 basket (BTC, ETH, XRP, SOL, BNB, DOGE, ADA, TRX, LINK, AVAX): USD median of Coinbase and Kraken, each source shown. $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/top10.

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

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 supplied, the description carries the full burden and does substantial work: it discloses price ($0.002 USDC), accepted payment chains (Base or Solana), no-account/no-API-key access, and that failed calls are not charged. Data provenance (median of two named exchanges) is also disclosed. It stops short of freshness/latency or rate-limit behavior.

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?

Front-loaded with 'Paid.' then what the data is, then cost and access mechanics, then the endpoint URL. No sentence is redundant and the whole definition is a few dense lines.

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 price call, an agent needs cost, access requirements, coverage, and provenance — all present. The only mild gap is the response shape beyond 'each source shown', which would help an agent plan parsing without an output schema.

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 applies. The basket membership acts as an implicit scoping statement, which is the only parameter-like information that could matter here.

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?

States the resource precisely (live crypto prices for a fixed top-10 basket) and enumerates the exact constituents (BTC, ETH, XRP, SOL, BNB, DOGE, ADA, TRX, LINK, AVAX), which alone distinguishes it from buy_crypto_price and buy_coin_* siblings. The aggregation method (USD median of Coinbase and Kraken) is also named, so an agent knows exactly what it is buying.

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 listed basket implicitly tells the agent to pick this tool when those ten assets are wanted, and the 'Paid' prefix signals it is the paid tier. However, it never explicitly contrasts itself with siblings such as buy_crypto_price (single coin) or buy_cp_majors, nor states when this basket is the wrong choice.

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