Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CHZ

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

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

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 the paid model, exact price ($0.01 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that data is Coinbase Exchange with a Kraken cross-check. It does not cover rate limits, caching/freshness, or the shape of an error response, 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.

Conciseness4/5

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

Front-loaded with the most decision-relevant fact ('Paid.') and then the payload, sources, and price. It is densely telegraphic — the field list and the payment terms sit in one run-on block — but no sentence is filler apart from the raw endpoint URL, which is of marginal use to an agent.

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 zero-parameter paid quote endpoint with no output schema and no annotations, the description covers the two things an agent most needs: what comes back (enumerated fields) and what it costs/requires. Remaining gaps are freshness, rate limits, and failure/error behavior beyond 'not charged'.

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 clarify beyond what the schema shows. The asset, quote currency, and granularity are all fixed and stated in the prose, which is adequate for a no-argument 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 payload: CHZ/USD last price, 24h open/high/low, % change, and 24h/30d volume, with data sources named. The ticker in the name disambiguates it from the hundreds of buy_coin_* siblings, but the description never says so explicitly (e.g., 'other assets use buy_coin_XXX'), so it stops short of a 5.

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 stated: an agent infers this is the tool for CHZ spot pricing. The text covers commercial/operational conditions (paid, $0.01, no API key) but gives no guidance on when to prefer buy_crypto_price or another sibling, nor any exclusion such as historical or non-USD quotes.

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