Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XAUT

Paid. Tether Gold (XAUT) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/XAUT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 a respectable job: it discloses the $0.05 USDC cost, the two accepted payment chains (Base, Solana), no account or API key required, and that failed calls are not charged. It stops short of the mechanics that matter for a paid endpoint — how payment is presented (e.g. an x402/402 challenge), what counts as a 'failed' call, and whether every successful response is billed.

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?

Six short fragments, front-loaded with price/paid status and ending with the URL — nothing is padded. The telegraphic style is efficient, though the run of clipped phrases reads more like a pricing banner than 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, no-annotation quote tool this covers the essentials an agent needs to decide and pay: what is returned, what it costs, on which chains, and that auth is unnecessary. Remaining gaps are the payment handshake and the response shape, which no other structured field supplies.

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 schema has zero parameters, so the baseline is 4 and the description correctly adds no parameter prose. The only extra addressing information is the endpoint URL, which is useful but not a parameter contract.

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?

States a specific resource (Tether Gold / XAUT) and the exact payload returned: live USD price, 24h change, and market-cap rank. That is far more than a restatement of the name. It does not differentiate itself from the hundreds of sibling buy_tok_* / buy_coin_* tools, so an agent must infer that other symbols live under other tool names.

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 is only implied by the payload description — an agent can reason it should call this when it needs an XAUT quote. There is no explicit when-to-use or when-not-to-use, and no pointer to the numerous price-related alternatives (buy_crypto_price, buy_coin_*, buy_tok_XAUM, buy_stable_*) that could also serve a gold/price request.

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