Skip to main content
Glama

SouthPow crypto & market data

buy_cp_memes

Paid. Live crypto prices, memes basket (DOGE, SHIB, PEPE, BONK, WIF, FLOKI, TRUMP, PENGU): 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/memes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does well: it discloses that the call is paid, the exact price ($0.002 USDC), the two accepted payment chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged. It does not describe latency, rate limits, or freshness guarantees, which keeps it short of a 5.

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 ("Paid." first, then coverage, then aggregation method, then price/access terms, then URL), and every clause carries signal. The sentence is dense and telegraphic, which suits a machine reader but slightly hurts readability.

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 endpoint, the description supplies what an agent needs: coverage, the aggregation methodology (USD median of Coinbase and Kraken with each source shown), price, payment rails, and the URL. Only the response shape and data freshness are left 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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly spends no words on arguments and instead front-loads the endpoint URL, which is the only invocation-relevant detail.

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 a named memes basket) and enumerates the exact eight tickers covered, so an agent can tell instantly whether its target asset is in scope. It is distinguishable from single-asset siblings like buy_coin_DOGE or buy_cp_dog-coins by the explicit basket membership list.

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?

Implied usage is clear (buy this endpoint when you want a multi-coin meme price snapshot), but there is no explicit when-to-use or when-not-to-use statement versus overlapping siblings such as buy_coin_PEPE, buy_coin_BONK, or buy_cp_dog-coins. The agent must infer the basket-vs-single-asset tradeoff on its own.

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