Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XION

Paid. Xion (XION) 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/XION.

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

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 disclose meaningful behavior: it is a paid call, settlement is in USDC on Base or Solana, no credentials are needed, and failed calls are not charged. It does not cover rate limits, latency, response shape, or what 'failed' means, so the commercial and failure semantics are only partially specified.

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?

The description is short and front-loads the most decision-relevant fact ('Paid') before the payload contents and price. The telegraphic fragments and trailing bare 'URL ...' are slightly rough, but no sentence 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?

For a zero-parameter, no-output-schema endpoint, the description supplies what an agent actually needs: the returned fields, the cost, the payment rails, and the auth model. Only the response format/units detail is thin, which is acceptable given the tool's simplicity.

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, which is the baseline-4 case; there is no input meaning for the description to add. The description correctly signals the tool is parameterless by pinning the asset in the name and the URL path.

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 the exact resource (Xion/XION) and enumerates what is returned: live USD price, 24h change and market-cap rank. That is far more specific than the bare name, but it never distinguishes this token endpoint from adjacent siblings such as buy_crypto_price (generic price) or the buy_coin_* family, so an agent must infer the boundary itself.

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?

Leading with 'Paid' plus the $0.01 USDC price implies the condition for use (only when the caller is willing to spend), and 'No account, no API key' removes setup friction. There is no explicit when-not-to-use and no named alternative (e.g., a free bulk price tool), so routing guidance is only implied.

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