Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ATH

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

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

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, the description carries the full behavioral burden and does so well: it discloses the exact cost ($0.01 USDC on Base), the payment chain, that no account or API key is needed, that failed calls are not charged, the upstream data sources (Coinbase Exchange with a Kraken cross-check), and the endpoint URL. What is missing is any statement of response shape/serialization or rate/refresh characteristics, which matters since there is no output schema.

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 short and front-loaded: 'Paid.' comes first, then the payload, then the price, then the trust guarantees, then the URL. The telegraphic fragment style ('Paid.', 'No account, no API key.') is dense but readable, and every clause carries information an agent needs before spending money.

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 data lookup with no output schema, the description covers cost, payment method, auth requirements, billing on failure, sources, and the fields returned — effectively standing in for the missing output schema. Remaining gaps are minor: no error/failure modes beyond billing, and no indication of update cadence or data freshness.

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. The description correctly implies nothing needs to be supplied, and the asset identity is baked into the tool rather than passed as an argument, which is consistent with the empty input schema.

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 a specific resource and payload: 'ATH/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'. Since the family is a per-symbol set of buy_coin_<TICKER> tools, naming ATH/USD is what distinguishes it from its hundreds of siblings. The paid/purchase framing is implied by 'Paid' and '$0.01 USDC on Base' rather than stated as a verb, which keeps it just below 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 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. A sibling generic price tool (buy_crypto_price) exists, and the description never says why an agent should pick this symbol-specific paid endpoint over it. Reassurances like 'No account, no API key' and 'Failed calls not charged' reduce friction but do not route the agent between alternatives.

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