Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZETA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 cost ($0.01 USDC on Base), settlement chain, absence of auth, and the no-charge-on-failure policy. It also names the upstream sources (Coinbase Exchange with Kraken cross-check), which is meaningful behavioral context. It stops short of stating latency, rate limits, or data staleness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the payment flag, then the payload, then the pricing/auth terms, then the endpoint URL. Every clause carries information an agent needs; there is no padding or restatement of the tool name.

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?

The tool has no input parameters and no output schema, so the description must define the return shape itself — and it does, by listing the exact fields returned. Cost, auth needs, and failure billing are all covered. Minor gap: no indication of response format (JSON shape/units) or freshness 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 baseline of 4 applies. Nothing is required of the caller beyond invocation, and the description supplies no misleading parameter terminology.

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?

States a concrete verb+resource ('ZETA/USD live' price retrieval) and enumerates exactly which data is returned: last price, 24h open/high/low, % change, 24h and 30d volume. The ticker in the name already separates it from the ~300 sibling buy_coin_* tools, so an agent can select the right one without opening a schema.

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, no account, no API key, failures not charged) that tell the agent this is a callable paid quote endpoint. However, it never says when to prefer this over alternatives such as the aggregated buy_crypto_price tool or which market conditions warrant a fresh call.

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