Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ARPA

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

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

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, the description still discloses the traits an agent most needs: it is paid ($0.01 USDC on Base), requires no account or API key, failed calls are not charged, and data comes from Coinbase Exchange with a Kraken cross-check. It omits rate limits, latency, and whether the payment is per-call or per-key, which keeps it below a 5.

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?

Front-loads the 'Paid' flag, then the data payload, then cost, auth, billing guarantee, and endpoint URL — every clause carries decision-relevant information. The telegraphic style is dense but readable; no filler sentences.

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?

With no input params and no output schema, the description must convey what comes back, and it does by listing the returned metrics and their sources. Cost and authentication are covered; the only real gap is the response shape/units (e.g., how % change and volumes are formatted).

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 usefully confirms that the ticker and pair are fixed rather than caller-supplied, which prevents an agent from trying to pass a symbol argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact pair (ARPA/USD) and enumerates the returned fields — last price, 24h open/high/low, % change, 24h and 30d volume — plus the venues. Despite the 'buy_coin_' prefix implying a purchase, the description makes unambiguously clear this is a live price-read for one specific ticker among the many sibling tickers.

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 statement of when to pick this over the generic sibling like buy_crypto_price, nor any exclusion or prerequisite ordering. The 'Paid' and '$0.01 USDC on Base' lines tell the agent the cost but not the decision rule for invoking it.

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