Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GST

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the call is paid ($0.25 USDC on Base), requires no account or API key, failed calls are not charged, and the endpoint URL is given. It omits rate limits, latency, and whether the charge occurs per call regardless of data freshness, which matters for a pay-per-call tool.

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 dense and front-loaded: cost and auth first, then the returned fields, then the endpoint. Every clause carries information, though the fragment 'Paid.' and the bare URL are terse enough to border on cryptic for a reader unfamiliar with the service.

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

Completeness3/5

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

There is no output schema, so the description must describe returns, and it enumerates the fields and their upstream sources reasonably well. It still leaves the response shape (JSON keys, numeric units, timestamp format, staleness) unspecified, which is a real gap for an agent parsing the result programmatically.

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

Parameters5/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; the schema is empty and the description correctly spends no words on inputs. Baseline for a 0-param tool is a 4, and the description adds the useful implied default that the pair is fixed at GST/USD.

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 states a concrete resource and payload: GST/USD live price with last price, 24h open/high/low, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). The ticker differentiation from siblings lives in the tool name, so the description needn't restate it, but it never clarifies that this is a data-retrieval call rather than an order-placement call despite the 'buy_coin_' prefix.

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 can infer it should call this when it needs GST spot/OHLC/volume data. There is no explicit when-not guidance and no routing against the sibling buy_crypto_price tool, which could be a cheaper or broader alternative. The payment and auth notes help the agent decide it *can* call, but not when it *should*.

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