Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CAKE

Paid. CAKE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.10 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CAKE.

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

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 full burden and does substantial work: it discloses the cost ($0.10 USDC on Base), the payment/auth model (no account, no API key), the failure policy (failed calls not charged), the data provenance (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It stops short of saying how payment is actually transacted or whether the data is real-time versus delayed.

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?

It is dense and front-loaded: the data contents appear first, then price, then auth, then the endpoint. The telegraphic fragments ('No account, no API key.') are efficient rather than sloppy, though the opening one-word 'Paid.' is slightly cryptic out of context.

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-param tool with no annotations and no output schema, the description covers purpose, content fields, cost, auth, failure policy, and endpoint. The remaining gap is the exact response shape and payment mechanics, which an agent paying per call might want.

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 avoids inventing parameter detail and instead spends its words on cost and output fields.

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?

The description names the exact resource and scope: CAKE/USD live price with an enumerated field list (last price, 24h OHLC, % change, 24h and 30d volume) and the underlying venues. Because the ticker is embedded in the tool name, this is enough to distinguish it from the hundreds of buy_coin_* siblings without opening a schema.

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?

It gives the conditions an agent needs to decide to call it (paid, no account, no API key, no charge on failure) but never names an alternative such as buy_crypto_price or a sibling ticker tool, nor states when this feed is preferred over the generic price tool. Usage is implied rather than prescribed.

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