Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZKC

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

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

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 so well: it discloses the cost and payment chain, that no auth is required, that failed calls are not billed, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the literal endpoint URL. It stops short of rate limits, expected latency, or response shape.

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-loads the billing flag ('Paid.') before the payload description, so cost is known before commitment, and packs fields, chain, auth, and URL into a few dense clauses with no filler. The telegraphed fragments ('No account, no API key.') read slightly stenographic but cost nothing in clarity.

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-output-schema paid quote tool, this covers what an agent must know before calling: price, chain, auth requirements, failure billing, and upstream sources. The one gap relative to the sibling set is the absence of any pointer to buy_crypto_price for multi-asset pricing.

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, which is the baseline-4 case. The description correctly adds none and instead spends its words on cost and data provenance, which is the right trade for a zero-arg paid endpoint.

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?

Names the exact resource (ZKC/USD live quote) and enumerates the payload fields it returns: last price, 24h open/high/low, % change, 24h and 30d volume. The operation is implicit rather than a stated verb ('fetch'), but among the many buy_coin_<TOKEN> siblings the pair identifier makes the tool's scope unmistakable.

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?

Gives useful preconditions — paid at $0.25 USDC on Base, no account or API key needed, failed calls not charged — which tell an agent whether it can invoke this. It never says when to prefer this over the apparent general sibling buy_crypto_price, nor any when-not-to-use condition, so routing between price tools 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