Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XRP

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the price ($0.10 USDC on Base), that no account or API key is needed, that failed calls are not charged, the upstream sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. These are exactly the facts an agent needs before spending money on a call. It omits rate limits and response shape, which keeps it off a 5.

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?

Extremely dense and front-loaded — the cost signal 'Paid.' leads, followed by payload contents, then pricing/auth/failure terms. It is telegraphic rather than gracefully written, and the raw URL is arguably redundant, but no sentence is padding and the ordering prioritizes what an agent needs first.

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, annotation-free tool with no output schema, the description supplies the payload fields, the monetary cost, the access model, the failure-charging policy, and data provenance. An agent could invoke it correctly and know the price of doing so. Only response format/units and any rate limits are absent, which keeps it just below complete.

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 per the baseline this scores 4; schema coverage is 100% and there is nothing for the description to disambiguate. The ticker is baked into the tool identity rather than passed as an argument, which is stated implicitly by the name and the XRP/USD framing.

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 a concrete resource (XRP/USD live price) and enumerates exactly what it covers: last price, 24h open/high/low, % change, 24h and 30d volume. Siblings are all ticker-suffixed variants, so the XRP scope is unambiguous. However, it never states an action verb, and the name 'buy_coin_XRP' implies a purchase while the content describes a data lookup — an agent must infer that this fetches price data rather than buys XRP.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not guidance is offered, and no routing against alternatives such as buy_crypto_price (a general price sibling) or fetching XRP data another way. The 'no account, no API key' line describes access prerequisites rather than selection criteria, so an agent has no basis for choosing this over a sibling beyond reading the 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