Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZEC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 this is a paid call, the exact cost and payment rail ($0.25 USDC on Base), that no credentials are required, and that failed calls are not charged — the key cost/risk facts an agent needs before invoking. It stops short of explaining the payment handshake mechanism, rate limits, or whether results are cached.

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?

The definition is front-loaded with the payment fact ('Paid.') and the data scope, then commercial terms, then the endpoint URL — a sensible order where nearly every fragment carries distinct information. The telegraphic style ('Paid.', bare URL) is terse to the point of mild ambiguity, which keeps it from a 5.

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 tool with no annotations and no output schema, the description supplies both the return-field inventory and the commercial/credential terms, which is what an agent needs to decide and call. Only the payment flow and response encoding are left unexplained.

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. The description implicitly confirms the ticker is fixed to ZEC and the quote currency is USD, which is useful framing for a zero-arg call.

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 a specific resource and scope (ZEC/USD live) and enumerates the exact data points returned: last price, 24h open/high/low, % change, 24h and 30d volume. Because every sibling is the same tool parameterized by a different ticker, the embedded ticker is what distinguishes it, and the description makes that unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes clear context for use: live spot data for ZEC from Coinbase with a Kraken cross-check, at a stated price of $0.25 USDC on Base with no account or API key. It does not explicitly route the agent to alternatives (e.g. the generic buy_crypto_price or a different ticker's tool) or state when not to use it, which keeps it below a 5.

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