Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BAT

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

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

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 substantial work: it discloses that the call is paid ($0.002 USDC on Base), requires no account or API key, and that failed calls are not charged, plus the upstream data sources. It leaves latency/freshness, response format, and any rate limits unstated.

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?

Roughly three compact sentences, front-loaded with the asset/pair, then data fields, then payment and access terms. The one-word 'Paid.' lead is terse but effective as a cost warning; nothing is redundant.

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, no-output-schema endpoint, the description adequately substitutes for a return schema by listing the returned fields and the source exchanges. What remains missing is freshness/latency and response encoding, which matter for a live price feed but are minor at this complexity.

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 cannot add meaning and the baseline of 4 applies. The description appropriately spends no words on parameter semantics and instead clarifies the implicit parameterization (fixed BAT/USD pair).

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 (BAT/USD live price) and enumerates exactly what comes back: last price, 24h open/high/low, percent change, and 24h/30d volume. That distinguishes it from other ticker siblings like buy_coin_BTC or buy_coin_ETH by asset, though it does not explicitly contrast with the generic buy_crypto_price aggregator.

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 only implied: an agent can infer it should call this when it needs a BAT spot price snapshot with multi-exchange coverage. There is no explicit when-to-use/when-not statement and no mention of when to prefer the sibling buy_crypto_price instead, which is a notable gap given the very large sibling set.

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