Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ACH

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/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 a decent job: it discloses the $0.01 USDC cost on Base, that no account or API key is needed, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It still omits rate limits, settlement mechanics (is the $0.01 paid automatically per call, via x402?), and whether quotes are cached or real-time at request time.

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 dense and front-loaded: payment status, data content, price, auth requirements, and endpoint all appear in one compact block with no filler. The telegraphic style ('Paid.', 'No account, no API key.') is efficient, though a slightly more explicit subject for the first sentence would improve parseability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description compensates by listing the returned fields, and it adds the payment model, cost, asset, auth posture, and raw URL. For a zero-parameter paid data endpoint, an agent has enough to decide whether to call it and what it will receive.

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 schema contributes nothing and the baseline is 4. The description correctly implies the asset and quote currency are fixed (ACH/USD) rather than configurable, which removes any expectation that the agent must supply a ticker.

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 concrete resource (ACH/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It also implicitly corrects the ambiguous 'buy_coin' name by making clear this is a paid price lookup, not a token purchase. It doesn't explicitly differentiate itself from the many identical sibling endpoints, though the ticker in the name does that work.

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: use this when you need live ACH/USD quotes. There is no explicit when-to-use or when-not framing, and no mention of the generic buy_crypto_price sibling that might cover the same need more cheaply across assets. The 'failed calls not charged' note does hint at retry safety.

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