Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZORA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 well: it discloses that the call is paid ($0.01 USDC on Base), requires no account or API key, that failed calls are not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency/staleness of the quote, and the error shape when upstream data is unavailable.

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 block is short and front-loaded: payment status first, then returned fields, then cost/auth/billing, then the endpoint URL. The telegraphic phrasing ("Paid.", bare URL, parenthetical source note) is dense but every clause carries information an agent needs to decide and pay.

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 price endpoint, the description covers the important ground: what fields come back, which exchanges back them, and the payment semantics. The main residual gap is the response format/error behavior, which is non-trivial for an agent that must budget a paid call.

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 in the schema the description needs to compensate for. The description correctly implies a parameter-free call keyed solely on the coin.

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 a specific resource and a precise payload: "ZORA/USD live: last price, 24h open/high/low, % change, 24h and 30d volume," which lets an agent tell this apart from the generic buy_crypto_price by coin and by field set. It never explains the relationship to the identically structured buy_coin_* siblings or to buy_crypto_price, and the tool name ("buy_coin_ZORA") misleadingly implies purchasing the asset rather than fetching a quote.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use statement and no alternative named — the agent must infer that this is the ZORA-specific quote endpoint versus buy_crypto_price. The sentences about account/API-key requirements and failure billing describe cost mechanics, not selection guidance.

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