Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ALT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With zero annotations, the description carries the full burden and does well on several axes: it discloses cost ($0.05 USDC on Base), payment rail, lack of account/API key requirements, and that failed calls are not charged. What it omits is anything about response latency, caching or data freshness, and whether the charge happens per call or per successful response, which matters for an agent deciding to retry.

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?

Two dense sentences with no filler; the data payload and the pricing terms are front-loaded. The telegraphic style ('Paid.', 'URL ...') is efficient, though a bare URL at the end is less useful than a field description would be.

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?

The description lists the returned fields, which is necessary because no output schema exists, and it covers the commercial terms. It is still thin on the operational side: no statement of response shape, units, or timestamp/freshness, which an agent needs when comparing the 30d volume or % change across calls.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so parameter semantics is not a meaningful axis here; baseline is 4. Since schema coverage is 100% and there is nothing to document, this dimension should not weigh against the tool.

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 the concrete resource and verb: live ALT/USD price with last price, 24h open/high/low, % change, and 24h/30d volume, plus the sources (Coinbase Exchange, Kraken cross-check). Among hundreds of per-asset siblings that share the same name pattern, the asset and the data fields make this tool's identity clear. It does not explicitly distinguish it from the generic buy_crypto_price sibling, 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 by the asset name and the field list: call this when you specifically need ALT/USD data. There is no explicit 'use this instead of buy_crypto_price/0' routing, no statement about staleness or rate limits, so an agent must infer that per-coin tools are the recommended path.

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