Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GEOD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses that the call is paid ($0.05 USDC on Base), requires no account or API key, and that failed calls are not charged — exactly the operational facts an agent needs before spending money. It adds upstream data provenance (Coinbase Exchange with Kraken cross-check) but omits latency, freshness guarantees, and response shape, keeping it below 5.

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?

Roughly three dense sentences with no filler; the cost and payment terms sit early, before the data description and the URL. The telegraphic style ('Paid.', 'GEOD/USD live:') and the trailing raw URL keep it from being maximally front-loaded and readable.

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?

For a parameterless, no-output-schema price endpoint, the description must convey the returned fields, and it does so explicitly (price, OHLC, % change, two volume windows). Combined with cost, payment chain, and auth requirements, an agent has enough to decide and invoke; only latency/response-format details are missing.

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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly spends no words on parameter explanation, leaving that budget for payment and content details.

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 (GEOD/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. That distinguishes it from the hundreds of sibling buy_coin_* tools, each of which covers a different asset. It stops short of a clean verb phrase and leaves the 'buy_coin_GEOD' name implying a purchase while the description describes a price-data read, so a 5 is not warranted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives such as buy_crypto_price or buy_coin_BTC for other assets. The payment and auth notes imply how to call it but never say which situations should route here rather than to a sibling.

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