Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XYO

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

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

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 behavioral burden and does so well: it discloses the paid model, exact price ($0.002 USDC on Base), that no account or API key is required, that failed calls are not charged, and that Coinbase Exchange is the primary source with a Kraken cross-check. What is missing is refresh cadence/latency and whether a payment failure vs. a data failure is handled differently.

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?

It is a tight, front-loaded fragment set: cost first, then payload contents, then payment terms, then endpoint. Nearly every clause carries information an agent needs. The telegraphic style (missing articles, colon-delimited lists) is efficient but slightly harder to parse than prose.

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 input schema and no output schema, the description must describe return values itself, and it does by listing the exact fields and their data sources. It stops short of specifying the response format (JSON shape), precision, or staleness of the 24h/30d figures, which an agent would need for reliable downstream use.

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 no parameter meaning to add and the baseline of 4 applies. The description does not waste space restating an empty schema, which is correct.

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 (XYO/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. It also reconciles the 'buy' verb in the tool name by stating 'Paid.' and the $0.002 USDC cost, so an agent understands this is a paid data purchase rather than an order-placement tool. It does not explicitly differentiate itself from the sibling buy_crypto_price or the per-token family, which keeps it below 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?

Usage is only implied: an agent infers it should call this when it needs XYO spot price data. There is no explicit 'use this instead of buy_crypto_price when...' routing, and no statement of when the tool is inappropriate, despite a large sibling set containing both a generic price tool and per-token variants.

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