Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZETACHAIN

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

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

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 load and does well: it discloses cost ($0.05 USDC on Base), payment rail, no account or API key required, and that failed calls are not charged — genuine preconditions an agent cannot infer otherwise. It also names the upstream data sources (Coinbase Exchange with Kraken cross-check) and the exact endpoint, which matters for trust. It stops short of stating update cadence or latency.

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?

Every fragment earns its place — price, cost, access model, billing policy, sources, URL — and the highest-stakes fact ("Paid") is front-loaded. The telegraphic list reads as compressed notes rather than prose, which slightly hurts scannability but wastes no words.

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-annotation tool with no output schema, the description covers the missing return-value burden itself by enumerating the returned fields, plus cost, authorization and sources. Only freshness/latency and response format are absent, which are minor for a price lookup.

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 nothing for the description to disambiguate and the baseline is 4. The description correctly implies a parameterless call by fixing the pair (ZETACHAIN/USD) and the endpoint URL itself.

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?

"ZETACHAIN/USD live" names a specific resource with a concrete field list (last price, 24h OHLC, % change, 24h/30d volume), so the agent knows exactly what data this returns. The ticker in the name also separates it from the hundreds of buy_coin_* siblings, though the description never states that sibling routing explicitly.

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?

The paid framing and $0.05 USDC price imply when it is worth calling versus free alternatives, but no alternative (e.g. buy_crypto_price or another ticker-specific buy_coin_* tool) is named and no explicit when-not-to-use condition is given. The pricing hook is real guidance, but the routing decision is 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