Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XAN

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

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

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 disclosure burden and does well: it states the price ($0.25 USDC on Base), the payment chain, that no account or API key is required, that failed calls are not charged, the upstream data sources, and the exact endpoint URL. What remains unsaid is the payment mechanics themselves (how the USDC charge is settled from a call) and rate limits or response format.

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-loading 'Paid.' is exactly right for a metered endpoint, and the remaining clauses are dense with load-bearing facts (fields, sources, cost, auth, refund policy, URL) with no filler. The telegraphic style borders on cryptic in places but never wastes a sentence.

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 tool, the description supplies what an agent actually needs: the data fields returned, the sources, the price, the auth model, and the endpoint. It is only slightly short of complete because the payment/settlement flow and response encoding are left to inference.

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; there is nothing for the description to disambiguate. The description does confirm the pair is fixed to XAN/USD, which tells the agent no symbol argument is needed.

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 states a specific verb-level outcome and resource: XAN/USD live pricing with enumerated fields (last, 24h open/high/low, % change, 24h/30d volume) and named sources (Coinbase Exchange, Kraken cross-check). This distinguishes it from sibling tickers via the XAN pair and from buy_crypto_price by the fixed pair and vendor. It does not reconcile the 'buy_coin_' naming with the fact that this is a read-only price endpoint, which leaves a small ambiguity.

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?

Usage context is implied by 'Paid. ... $0.25 USDC on Base. No account, no API key. Failed calls not charged,' which tells an agent the preconditions for calling. However, there is no explicit guidance on when to prefer this over buy_crypto_price or another ticker's endpoint, and no statement of when not to 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