Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ABT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 well: it discloses the pricing model and exact cost, the payment chain/currency, the absence of auth requirements, the failure-billing policy, and the upstream data sources. Gaps remain around rate limits, latency, and response shape (JSON structure beyond the field list).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Extremely dense but front-loaded: payment status leads, then the returned data, then sources, then cost, then access requirements, then endpoint. Every clause carries distinct information — no filler sentences and no repetition of the tool name.

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 endpoint with no annotations and no output schema, the description covers what an agent needs: what data comes back, where it comes from, what it costs, that failures are free, and that no key is required. Only the response encoding and any rate/frequency constraints are left unstated.

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 of 4 applies. The description correctly implies no inputs are needed by presenting the ticker as fixed in the tool identity and giving no argument hints.

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 states a specific resource and dataset: ABT/USD live price with last, 24h open/high/low, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). This distinguishes it from sibling per-asset tools like buy_coin_AAVE implicitly through the ticker. It stops short of explicitly naming the sibling pattern (e.g., 'for other assets use buy_coin_<TICKER>'), so it is clear but not fully self-routing.

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?

The description supplies decision-relevant context — 'Paid', '$0.002 USDC on Base', 'No account, no API key', 'Failed calls not charged' — which tells an agent the cost and prerequisites of invoking it. However, it never states when to prefer this over alternatives (e.g., buy_crypto_price or a free sibling), nor any when-not conditions. Usage is implied rather than instructed.

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