Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BARD

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

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

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 disclosure burden and does it well: it states the tool is paid, the exact cost and asset ($0.05 USDC on Base), that no auth is needed, that failures are not charged, and that data is cross-checked across Coinbase Exchange and Kraken. It stops short of describing latency, rate limits, or failure modes beyond billing.

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?

Telegraphic but dense, with the payment caveat front-loaded so the agent sees the cost before anything else. The trailing bare URL is minor clutter but harmless context.

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 endpoint with no output schema, the description enumerates the returned fields and covers cost, auth, and billing behavior. Only secondary operational details (latency, rate limits, response format) are absent.

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 fixed ticker and endpoint being baked into the description is consistent with that and leaves nothing for the agent to supply.

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 states precisely what the tool returns (BARD/USD last price, 24h OHLC, % change, 24h/30d volume) and names its data sources, so an agent knows exactly what it gets. It does not explicitly resolve the tension between the 'buy_coin_' name and a description that describes a paid price lookup rather than a trade, leaving the 'buy' mechanic implicit in '$0.05 USDC on Base'.

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?

It supplies useful context for deciding to call it (no account or API key required, failed calls not charged) but never says when to prefer this over sibling tools such as buy_crypto_price or the many other buy_coin_* endpoints, nor does it state exclusions.

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