Skip to main content
Glama

SouthPow crypto & market data

buy_coin_2Z

Paid. 2Z/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/2Z.

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

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 supplied, the description carries the full burden and does well: it discloses the cost, the settlement currency and chain, the absence of authentication requirements, and the refund behavior ('Failed calls not charged'). What it omits is the response shape beyond the field list, latency, and what an unsuccessful call actually looks like to the agent.

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?

Telegraphic and front-loaded: 'Paid.' appears first so cost awareness precedes anything else, followed by the payload, then the price/auth terms, then the endpoint. Nothing is padded, though the fragment style ('Paid.', bare URL) trades a little readability for density.

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 appropriately enumerates the returned fields itself, and it covers the payment and auth model that would otherwise be unknown. For a no-parameter, single-fetch tool the only real gap is failure/error behavior beyond the no-charge guarantee.

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 description has no parameter semantics to explain and cannot be faulted for that. It instead uses the space to describe the fixed request the tool issues (a specific asset pair against named exchanges), which is the natural equivalent for a parameterless 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?

The description names the exact asset pair (2Z/USD) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume, plus the sources (Coinbase Exchange, Kraken cross-check). That is enough to separate it from the ~400 sibling buy_coin_* tools that differ only by ticker. It lacks an explicit verb, and it does not explain how it differs from the generic buy_crypto_price sibling, so it stops short of a 5.

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?

Payment terms imply the usage context — the agent learns this call costs $0.05 USDC on Base and needs no account or API key, which is the decisive precondition for calling it. However, there is no explicit statement of when to prefer this over buy_crypto_price or another ticker-specific tool, and no guidance on repeated polling or caching.

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