Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ARX

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

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

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, the description carries the full burden and does notable work: it discloses that the call is paid, the exact price and chain, that no authentication is required, and that failed calls are not billed. Gaps remain around latency/data freshness, rate limits, and the mechanics of the payment step (whether settlement precedes the response).

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?

Terse and front-loaded — 'Paid.' and the cost signal appear before the payload description, which is the right order for an agent weighing spend. The telegraphic fragments are efficient, though the bare 'Paid.' opener is slightly cryptic without a subject, and the raw URL is of marginal use to a caller that cannot set it.

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?

There is no output schema, so the description must describe return values itself — it does so field by field, including the cross-checked sources. With no annotations it also covers the commercial and auth surface. What is missing (freshness, response encoding, error shapes) is modest for a fixed-endpoint price lookup.

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; the baseline applies. The description correctly implies a parameterless call by quoting a fixed endpoint URL.

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 specific resource (ARX/USD live price data) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, plus the upstream sources. It is distinguishable from the ~300 buy_coin_* siblings only by the ticker, but within that family the scope is unambiguous. The 'buy' verb in the name is really a payment step rather than a purchase, which the description does clarify via the $0.05 USDC line.

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?

Cost ($0.05 USDC on Base), the absence of an account or API key, and the no-charge-on-failure policy give an agent clear preconditions before spending. However, it never states when to choose this over buy_crypto_price or another coin tool, nor when ARX data is not worth the fee. Usage is implied by the ticker rather than explained.

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