Skip to main content
Glama

SouthPow crypto & market data

buy_cp_ethereum-ecosystem

Paid. Live crypto prices, ethereum ecosystem basket (ETH, LDO, UNI, AAVE, ENS, LINK, ARB, OP): 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/ethereum-ecosystem.

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_ethereum-ecosystem"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 substantial work: it discloses the paid model, the exact price and accepted payment chains, that no auth is required, that failures are not billed, and the aggregation method (USD median of Coinbase and Kraken, each source shown). It does not cover rate limits, latency, or freshness/staleness of quotes, which are the remaining behavioral gaps for a priced feed.

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.' so the cost constraint is the first thing an agent sees, then scope, then methodology, then payment terms. Dense semicolon-separated clauses with no filler sentences; the URL is the only trailing element and is operational, not padding.

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 paid feed with no output schema and no annotations, the description covers what is being sold, what data backs it, what it costs, how to pay, and how failures are handled. The one shortfall is that it does not sketch the response shape beyond 'each source shown', which matters because there is no output schema to fall back on.

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 no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The basket membership list effectively documents the implicit 'input' (which assets are covered), which is a mild value-add over an empty schema.

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 a specific verb+resource: live crypto prices for an 'ethereum ecosystem basket', and enumerates the exact constituents (ETH, LDO, UNI, AAVE, ENS, LINK, ARB, OP). That constituent list cleanly separates it from sibling baskets like buy_cp_majors, buy_cp_defi, and buy_cp_base-ecosystem without the agent needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this applies: a paid endpoint at $0.005 USDC on Base or Solana, with no account or API key needed, and failed calls not charged (a useful retry signal). It does not explicitly route away from alternatives — e.g. it never says to use buy_coin_ETH for a single coin or buy_cp_defi for a broader DeFi list — so the exclusions are left to inference.

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