Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XPL

Paid. XPL/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/XPL.

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

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, the description carries the full burden and does well: it discloses price ($0.05 USDC on Base), payment rail, absence of auth, the failed-call-no-charge policy, and the underlying feeds including a Kraken cross-check. It omits the mechanics of the payment handshake (e.g., how the 402 challenge is settled) and latency/freshness guarantees.

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?

Terse and front-loaded – 'Paid.' flags the cost model immediately, then payload, then price/auth/failure terms, then endpoint. No sentence is filler, and the telegraphic style suits a machine-read definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 describe return values, and it does list the fields returned, but not the response shape (JSON envelope, field names, units, timestamp fields). For a paid, stateless fetch tool the coverage is adequate but leaves the agent guessing at the response format it is paying for.

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 the baseline is 4 and there is nothing the description needs to disambiguate. It correctly spends no words on input semantics.

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: XPL/USD last price, 24h OHLC, % change, 24h and 30d volume, with named data sources. It clearly identifies the asset among the many buy_coin_* siblings via the ticker, though it never explicitly contrasts itself with buy_crypto_price, which is the obvious cross-asset alternative.

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?

Provides access conditions ('No account, no API key', failure not charged) but no when-to-use routing: nothing says whether to prefer this over the multi-coin sibling buy_crypto_price or when a real-time quote is warranted versus a cached one. Usage is implied by the ticker-specific naming rather than stated.

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