Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XDC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does a solid job: it discloses that the call is paid, the exact price and accepted payment chains, that no credentials are needed, that failures are not billed, and the underlying endpoint URL. Not covered: rate limits, latency, or whether the price data is cached/delayed -- the remaining behavioral unknowns.

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?

Dense and front-loaded: 'Paid.' flags the cost model immediately, then scope, then payment terms, then endpoint. Every sentence carries information. The bare 'URL https://...' fragment is slightly telegraphic but still efficient rather than 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?

With no output schema and no annotations, the description must cover both what comes back and the commercial terms, and it does: three named return fields plus price, payment chains, and billing behavior. The only gap is that field shapes (e.g. rank as integer, change as percent) are not specified, which matters somewhat since no output schema exists.

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 for the description to disambiguate; the baseline for a parameterless tool is 4. It correctly implies no input is needed, since the asset is fixed by the tool name itself.

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?

Names a specific resource and verb: XDC Network (XDC) price, with the exact payload (live USD price, 24h change, market-cap rank). That is far more specific than a generic 'get price'. It stops short of 5 because it never contrasts itself with the generic sibling buy_crypto_price, which an agent could equally pick for the same request.

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?

Gives practical invocation context -- paid, $0.05 USDC on Base or Solana, no account or API key, failed calls not charged -- which tells the agent what it costs and what prerequisites exist. It offers no when-to-use/when-not guidance relative to buy_crypto_price or the other per-token buy_tok_* tools, so selection must be inferred from the token ticker in the name.

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