Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ADA

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

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

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 zero annotations the description carries the full burden and does well: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, that failures are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It omits the payment mechanics (how the USDC charge is settled), rate limits, and response shape, which are the remaining behavioral gaps.

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?

Extremely dense but every clause carries information: data fields, sources, price, auth requirements, billing policy, endpoint. The leading fragment 'Paid.' is slightly abrupt but front-loads the most decision-relevant fact. Minor weakness: the endpoint URL is included while the payment protocol is not, a slightly odd priority.

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 output schema and no annotations, the description must explain both the return payload and the invocation prerequisites, and it does: it lists the returned fields and the cost/auth/billing constraints. Completeness would be 5 if it explained how the $0.10 payment is executed on Base, since an agent needs that to actually complete a paid call.

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 no parameters, so there is nothing for the description to disambiguate; baseline is 4. The description appropriately spends its words on scope and cost instead of inventing parameter documentation.

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 a concrete resource (ADA/USD live price) and enumerates the exact fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. This distinguishes it from the ~400 sibling coin tools by ticker. It never clarifies how it relates to the generic buy_crypto_price sibling, so differentiation is only partial.

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?

There is no explicit when-to-use/when-not-to-use text and no routing to alternatives such as buy_crypto_price for non-ADA pairs. Usage is strongly implied by the single-asset scope, and the cost disclosure ('$0.10 USDC on Base', 'Failed calls not charged') gives the agent a real decision input before 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