Skip to main content
Glama

SouthPow crypto & market data

buy_coin_UNI

Paid. UNI/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/UNI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 that the call is paid, the exact cost ($0.10 USDC on Base), the payment network, that no account or API key is needed, and that failed calls are not charged. The remaining gaps are latency, rate limits, and how payment is actually settled (x402 handshake), which an agent wiring up a paid call would still want.

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: 'Paid.' lands first so cost is known before anything else, then payload, price, and terms. Every fragment carries information, though the trailing bare URL is of marginal use to an agent that cannot browse.

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?

No output schema exists, and the description compensates by enumerating the exact return fields, so the agent knows what comes back. Combined with the cost and auth disclosures, an agent can call this correctly; only payment-settlement mechanics and data freshness are absent, which are minor for a zero-parameter quote endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema baseline of 4 applies and there is nothing for the description to disambiguate. It adds no parameter-level meaning because none is possible; the description's value sits in the payload list instead.

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 asset pair and the exact payload: 'UNI/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus the sources (Coinbase Exchange, Kraken cross-check). That is a concrete verb-less but unambiguous read operation. It never names the sibling it differs from (buy_crypto_price, which appears to cover multiple coins), so differentiation rests entirely on the ticker suffix in the tool name.

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?

'Paid.' plus the price, network, and 'No account, no API key' gives the agent enough to decide the call is cheap and frictionless, so usage is implied. There is no explicit when-not-to-use, no statement about when to prefer buy_crypto_price or a free alternative, and no guidance on freshness or how often to re-call for live data.

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