Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XEF

Paid. Xeffy (XEF) 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/XEF.

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

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 well: it discloses payment amount, accepted chains/currency, absence of auth/API-key requirements, and the favorable failure policy (failed calls not charged). It stops short of describing the response shape or freshness/rate-limit guarantees beyond "live."

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?

Five short fragments, front-loaded with "Paid." so cost is known before anything else. Payment terms, auth posture, billing policy, and the endpoint URL each appear once with no filler.

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 no-param, no-output-schema purchase endpoint, the description supplies what an agent needs: what data comes back, what it costs, how to pay, and that failures are free. A brief note on response format or data freshness would close the remaining gap.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The token symbol is baked into the tool rather than a parameter, which is consistent.

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 and payload: "Xeffy (XEF) price: live USD price, 24h change and market-cap rank," plus that it is a paid call. The token is unambiguous, though the description never contrasts itself with generic siblings like buy_crypto_price or buy_coin_XEF, leaving sibling differentiation to the tool 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?

Conveys the cost context ($0.05 USDC on Base or Solana, no account or API key, failed calls not charged), which implicitly tells an agent this is a per-call paid lookup. It never says when to choose it over buy_crypto_price or buy_coin_XEF, and gives no guidance on when the paid price feed is worth the spend.

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