Skip to main content
Glama

SouthPow crypto & market data

buy_coin_00

Paid. 00/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/00.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 well on the monetization/auth dimension: it discloses the $0.002 USDC-on-Base price, that no account or API key is needed, and that failed calls are not charged — rare and useful context. It stops short of rate limits, latency, retry/idempotency behavior, or what a failure response contains, so the behavioral picture is only partially filled in.

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?

Front-loading 'Paid.' immediately warns of cost, then the payload fields, then price/auth terms, then the endpoint URL — a sensible ordering with essentially no filler. The telegraphic style ('Paid. 00/USD live:') is dense but still parseable; minor loss for the lack of an explicit verb.

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?

With no parameters and no output schema, the description compensates well by enumerating the returned fields and their data sources, plus cost and auth requirements. Gaps are limited to error/response-shape detail and the ambiguity of what '00' denotes as an asset, which is a moderate but not crippling omission for a zero-parameter endpoint.

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 schema leaves nothing to interpret and the baseline applies. The description correctly implies the call is fixed to the 00/USD pair rather than parameterizable, which prevents an agent from trying to pass a symbol argument.

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 enumerates exactly what the tool returns for the 00/USD pair (last price, 24h OHLC, % change, 24h/30d volume) and names the upstream sources, so the resource and payload are unambiguous. It is weaker on the verb and on sibling differentiation — with hundreds of buy_coin_<TICKER> siblings, the only distinguishing token is '00', and the description never states explicitly that it retrieves a price snapshot rather than executing a trade (the 'buy_' prefix could mislead).

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?

Usage is only implied: an agent can infer this is the per-coin live price endpoint and that it requires no account or key. There is no explicit when-to-use, no when-not-to-use, and no reference to the generic sibling buy_crypto_price or to any alternative for multi-coin lookups, leaving routing 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