Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XDP

Paid. Doppler Finance (XDP) 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/XDP.

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

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 supplied, the description carries the full behavioral burden and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits and response shape, but payment, auth and failure semantics are exactly the traits an agent needs before spending money.

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?

Telegraphic but front-loaded: the paid flag and the data returned come first, followed by price, payment rails, auth, failure policy and URL. Every fragment carries information; the style is terse rather than padded, though slightly more connective phrasing would improve readability.

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 paid lookup with no output schema, the description supplies the returned fields, the cost, the payment chains, the auth requirement and the endpoint URL — essentially everything needed to decide and invoke. Only the response format and freshness/staleness of the price are unaddressed.

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 to disambiguate and the baseline of 4 applies. The description correctly implies no inputs are needed by giving a fully-qualified URL with the token baked in.

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: 'Doppler Finance (XDP) price: live USD price, 24h change and market-cap rank.' The token symbol in the name plus the explicit URL make the scope unambiguous. It does not explicitly route away from the hundreds of sibling buy_tok_* / buy_coin_* endpoints, so sibling differentiation is only implicit via the symbol.

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 description conveys when this is appropriate by describing the exact data returned (USD price, 24h change, market-cap rank), so an agent can match it to a price lookup. However, it never names an alternative such as buy_crypto_price or buy_coin_XDP, nor states when NOT to use this paid endpoint, which matters in a catalogue with near-duplicate siblings.

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