Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PROVE

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

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

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 that the call is paid, the exact price ($0.25 USDC on Base), that no account or API key is needed, and that failed calls are not charged. Remaining gaps are rate limits, payment-failure behavior, and data freshness/latency.

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?

Front-loaded with the single most important fact ('Paid.') followed by payload, price, and access terms in one dense sentence plus a URL. The telegraphic style is efficient, though abbreviations like '% change' and the appended raw URL are slightly cryptic at a glance.

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 and no annotations, yet the description covers cost, payment rail, auth requirements, billing failure policy, data sources, and returned metrics. For a simple zero-arg data fetch this is close to complete; only response format and freshness are unstated.

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-parameter tool, so baseline is 4. The description instead documents the response payload (last price, 24h OHLC, % change, 24h and 30d volume), which is useful since no output schema exists.

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 pair: 'PROVE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus the data sources (Coinbase Exchange, Kraken cross-check). It is clearly a price-snapshot endpoint for one asset, though it never explicitly says 'use the matching buy_coin_<SYMBOL> sibling for a different asset', leaving the sibling relationship implied by the 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?

Usage is implied rather than prescribed: the tool is for PROVE/USD pricing and the '.P' name pads out hundreds of per-asset siblings. The description adds commercial conditions (paid, $0.25 USDC on Base, no account/API key, failures not charged) but gives no explicit when-to-use/when-not guidance or comparison to alternatives like buy_crypto_price or buy_coin_PRO.

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