Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XAUM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 it well: it discloses that the call is paid ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It even lists the returned metrics. Missing only rate-limit or latency details, which are minor here.

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-loaded with 'Paid.' then purpose, then cost and auth terms, all in a few short clauses with no filler. Every sentence conveys something an agent needs before invoking a metered endpoint.

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-param, no-output-schema tool, the description covers what the endpoint returns, what it costs, how to pay, and that failures are free – enough to call it confidently. It could add the response shape (JSON keys/units) but the named metrics largely cover that.

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 are no arguments whose meaning could be lost. The description correctly implies a fixed, argument-free call for the XAUM asset, consistent with the empty schema.

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 (Matrixdock Gold / XAUM) and the exact data returned: live USD price, 24h change, and market-cap rank. It distinguishes the tool from the hundreds of sibling buy_tok_* tools by naming the underlying asset and issuer. The only weakness is that the verb is implicit – 'price' reads as a fetch, while the name says 'buy'.

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?

The 'Paid' framing and pricing hint at when this applies (a metered call for this specific token), but there is no explicit statement of when to choose this over siblings like buy_crypto_price or buy_tok_XAUT, nor any exclusion or prerequisite guidance. Usage is inferable from the asset name alone.

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