Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BNKR

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

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

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 carries the full behavioral burden and does substantial work: cost ($0.25 USDC on Base), payment chain, no authentication required, and the important failure policy that failed calls are not charged. Missing are rate limits, latency, and any indication of what an error response looks like, which keeps it out of the top band.

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?

Dense and front-loaded: cost and access first, then data content, then billing policy, then endpoint URL. Every clause carries information, though the telegraphic 'Paid.' opener and appended bare URL are a bit clipped for an agent parsing prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 paid endpoint, the description covers the four things an agent needs: what data comes back, what sources it reflects, what it costs and how to pay, and that failures are free. Nothing material is missing for correct invocation.

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 beyond confirming that the ticker and quote currency are fixed. Baseline 4 applies for a parameterless tool; the explicit 'BNKR/USD' phrasing usefully fixes what an agent gets without arguments.

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 exact resource (BNKR/USD spot price) and enumerates the returned metrics: last price, 24h open/high/low, % change, 24h/30d volume, plus the upstream sources (Coinbase Exchange, Kraken cross-check). That is far more specific than the bare ticker in the tool name, which misleadingly reads as a purchase action. It stops short of explicitly contrasting itself with the generic sibling buy_crypto_price.

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 context is implied by the pricing and access notes (paid per-call, no account or API key needed), so an agent knows it can call it without setup. However, there is no explicit when-to-use/when-not guidance and no mention of the obvious alternative buy_crypto_price or the other per-ticker siblings, leaving routing to inference.

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