Skip to main content
Glama

SouthPow crypto & market data

buy_coin_APE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 most of it well: it discloses the price ($0.002 USDC on Base), payment chain, the no-auth requirement, and a failure policy ('Failed calls not charged'). What it omits is the response shape/timestamps and whether data is cached or delayed, which matters for a live price feed.

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 compact and front-loaded: data content first, then price/auth/failure terms, then the URL. The telegraphic style ('Paid.', missing verb) is efficient but slightly terse, and mixing the endpoint URL into prose makes it marginally harder to scan than a clean sentence plus a labeled URL.

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?

There is no output schema, so the description helpfully enumerates the returned fields and their sources, and it covers the two things an agent most needs to decide on a paid call: cost and failure charging. The remaining gap is the exact response format and freshness guarantees, which an agent would want before paying per request.

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 no parameter semantics to explain and the baseline is 4. The description correctly adds nothing parameter-related, instead spending its words on data content and cost.

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 states precisely what data is returned for APE/USD: last price, 24h open/high/low, percent change, and 24h/30d volume, plus the source exchanges. The ticker-specific scoping distinguishes it from the ~400 buy_coin_<TICKER> siblings without needing to name them. The only weakness is that the leading 'Paid.' and the verbless phrasing make the core purpose slightly less front-loaded than it could be.

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 implies usage via 'Paid' and the cost line, and 'No account, no API key' tells the agent there are no prerequisites, which is real guidance. However, it never says when to choose this over a general alternative like buy_crypto_price or when a cross-checked Coinbase/Kraken feed is preferable to another ticker tool. Usage context is implied, not stated.

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