Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ATOM

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

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

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 at all, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that Coinbase Exchange is the primary source with a Kraken cross-check. It stops short of rate limits or explicit response format/error behavior, which keeps it off 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?

The cost signal is front-loaded ('Paid.'), followed by payload contents, then payment/auth terms, then the endpoint URL — a sensible order with no padding. The clipped, telegram-style fragments read less smoothly than full sentences but every clause carries information.

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, no-output-schema paid endpoint, the description supplies what an agent actually needs to decide and act: what data comes back, what it costs, that no credentials are required, and that failures are free. The only gap is lack of any note on rate limits or the response encoding, which is minor given the enumerated fields.

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 nothing for the description to disambiguate; that is the baseline-4 case. The description correctly does not invent parameter guidance.

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 exact resource (ATOM/USD) and enumerates the returned fields: last price, 24h open/high/low, percent change, 24h and 30d volume. That is specific enough to separate it from the hundreds of sibling symbol tools. It is slightly weaker than a clean verb+resource statement because the phrasing is telegraphic ('Paid. ATOM/USD live: ...') rather than an explicit action.

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 the data listed (call it when you need ATOM spot stats), and the cost/auth terms are stated. However, it never says when to prefer this over alternatives such as buy_crypto_price, and it gives no condition under which the tool should not be used, so routing remains inferential.

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