Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BIRB

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden, and it does substantial work: discloses the cost ($0.10 USDC on Base), the payment rail, the free-on-failure policy, the absence of auth requirements, the upstream sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. Missing is any indication of latency/freshness or how the payment flow is actually presented to the caller.

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?

Compact and front-loaded: cost and data fields come first, commercial terms follow. The telegraphic style ('Paid.', arrow-less field list) is efficient but borders on cryptic, and the URL could be considered metadata rather than description content.

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 tool with no output schema, the description lists the returned fields and states the pricing, auth, and failure-charge model — enough for an agent to decide and call. Residual gaps (how payment is settled, data staleness) are modest for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 to disambiguate and the baseline applies. The description adds the literal endpoint URL, which is mildly useful for transparency but does not function as parameter semantics.

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?

States the specific resource (BIRB/USD live price) and enumerates exactly what data is returned: last price, 24h open/high/low, % change, 24h and 30d volume. This clearly distinguishes it from non-BIRB siblings in the buy_coin_* family and from buy_crypto_price. It stops short of naming a sibling alternative, but the pair-level specificity is high.

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?

Implicit usage is clear: call this when you need BIRB/USD spot data. It also usefully states there is no account or API key and that failed calls are not charged, which is selection-relevant context. However, it never says when to prefer this over buy_crypto_price or how to handle a scenario where a different ticker is desired — guidance is implied rather than explicit.

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