Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XPR

Paid. XPR Network (XPR) 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/XPR.

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

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?

No annotations are supplied, so the description must carry the full behavioral burden, and it does well: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is needed, and that failed calls are not charged. What it omits is the return shape beyond field names and any rate limit or latency characteristics.

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?

The single most decision-relevant fact ("Paid") is front-loaded, followed by what you get, what it costs, and where to call it. Every sentence carries information an agent needs; nothing is padded.

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-parameter paid data endpoint with no output schema, the description covers what is returned, the payment model, and the endpoint URL, which is enough to invoke correctly. It could be slightly more complete by noting response format (e.g., JSON) or freshness guarantees.

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 there is nothing beyond the schema to clarify; the baseline for a parameterless tool applies. The description does not need to explain inputs and correctly spends its words elsewhere.

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 specific resource (XPR Network / XPR) and enumerates the returned fields: live USD price, 24h change, market-cap rank. That is a clear verb+resource picture of what a call yields. It stops short of differentiating from adjacent siblings such as buy_crypto_price or buy_coin_* families, which is the main reason it is not a 5.

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?

There is clear context for how to transact (cost, chains, no account or API key) but no statement of when to choose this over buy_crypto_price or another token endpoint, and no exclusions. Usage is implied by the token name rather than explained.

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