Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZK

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

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

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 it does disclose the important operational traits: $0.10 USDC on Base, no account or API key required, failed calls not charged, and Coinbase Exchange as source with a Kraken cross-check. What it omits is return shape, freshness/staleness of quotes, latency, and what happens on a partial or ambiguous failure — meaningful gaps for a metered call.

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 front-loaded with the two things that matter most — that the call is paid, and what data it returns — followed by price, auth, failure policy, and endpoint. The raw URL is of marginal value to an agent and the telegraphic fragment style ('Paid.', 'No account, no API key.') trades readability for density, but almost nothing is wasted.

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 usefully enumerates the returned fields and adds cost, auth, and failure-charge policy — enough for an agent to invoke the tool correctly. It stops short of describing the response envelope or data freshness, which would fully close the loop for a metered data 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 there is no parameter meaning for the description to add; the baseline for a 0-param schema applies.

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 names the resource (ZK/USD live price) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. The symbol is also encoded in the tool name, so an agent can distinguish it from the ~350 sibling buy_coin_<SYMBOL> tools, though it never states the verb ('fetch a paid price quote') outright or explicitly contrasts with buy_crypto_price.

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 implied rather than stated: it is a paid per-symbol quote endpoint, and the cost/auth/failure terms give an agent the context needed to decide whether to spend. However, it never says when to prefer this over the generic buy_crypto_price sibling, nor whether the call is worth repeating or caching, so the when-to-use 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