Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XTZ

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

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

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 cost, payment chain/currency, absence of auth requirements, and the failed-call billing policy, plus the direct endpoint URL and data provenance. It stops short of stating freshness/caching or rate limits, which would matter for a price feed.

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?

Very compact and front-loaded with the cost/paid signal, then the data content, then logistics. The leading fragment 'Paid.' is terse to the point of being cryptic before the price is given later, but 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?

No output schema exists, so the description must describe returns, and it does so field by field; payment and auth details are also covered. Missing only ancillary behavior such as data staleness or error semantics beyond 'failed calls not charged'.

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. The description compensates by enumerating the exact outputs the call yields, which is more than the empty schema conveys.

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 a concrete resource and scope: XTZ/USD live data with an explicit field list (last price, 24h open/high/low, % change, 24h and 30d volume) and the upstream sources (Coinbase Exchange, Kraken cross-check). It does not explicitly contrast itself with buy_crypto_price or state that it is the XTZ-specific variant among the buy_coin_* family, leaving that to the name.

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 operational prerequisites instead of selection guidance: it is paid ($0.25 USDC on Base), requires no account or API key, and failed calls are not charged. It never says when to prefer this over buy_crypto_price or the generic buy_crypto_price-style sibling, so the when-to-use decision is only implied by the symbol in the name.

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