Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GHST

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does well: it declares the call is paid ($0.25 USDC on Base), requires no account or API key, and that failed calls are not charged — precisely the cost/auth/failure semantics an agent needs before spending money. It omits latency, cache/freshness behavior, and response shape, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely dense and front-loaded: 'Paid.' flags the cost model first, then data fields, then payment/auth terms, then the URL. Every fragment earns its place and nothing is repeated from structured fields.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description voluntarily enumerates the returned fields and their sources, plus pricing and failure-billing terms — everything an agent needs to decide whether to spend $0.25 on this call. Only minor details like refresh cadence are absent.

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 semantics to explain; the baseline for a 0-param tool is 4. The description correctly implies everything (asset, quote currency) is baked into the endpoint.

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 scope: GHST/USD live price with named fields (last, 24h OHLC, % change, 24h/30d volume) and named sources (Coinbase Exchange with Kraken cross-check). What it does not do is reconcile the 'buy_coin_' verb with the fact that the tool delivers a price feed rather than executing a purchase — the $0.25 USDC mention hints at a paid x402 endpoint, but an agent must infer whether anything is actually bought.

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 by content (fetch live GHST/USD market data), and the description does not name any alternative such as buy_crypto_price for multi-asset lookups or explain when-not to call. For a 500-sibling family where the only differentiator is the ticker, the implicit routing is probably enough, but no explicit guidance is given.

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