Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BILL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 burden and does well: it discloses the $0.01 USDC-on-Base payment, that no account or API key is required, that failed calls are not charged, and which exchanges supply the data (Coinbase Exchange with Kraken cross-check). It omits latency/staleness of quotes and how payment is actually transacted, which are the remaining behaviors an agent would want to know.

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?

Telegraphic, dense, and front-loaded: 'Paid.' comes first because it is the gating fact, then data scope, then price, then access terms, then the URL. Every fragment contributes and nothing is padded.

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?

No output schema exists, so the description must describe returns, and listing the exact fields (last, open/high/low, % change, 24h and 30d volume) plus the source venues does that adequately for a single-endpoint read. It stops short of stating response shape, quote freshness, or error semantics beyond 'failed calls not charged'.

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 and the baseline of 4 applies. The description correctly implies the call is parameterless by embedding the asset and endpoint directly in the tool identity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (BILL/USD live price) and enumerates the exact metrics returned (last price, 24h OHLC, % change, 24h and 30d volume), so the agent knows precisely what comes back. Among hundreds of near-identical buy_coin_* siblings the ticker in the name and description pin it to one asset without ambiguity.

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 implied by the data listed (call it when you need BILL/USD spot data), and the paid/gated framing tells the agent the prerequisite cost up front. However, it never states when NOT to use it or names the obvious alternative, buy_crypto_price, which likely serves the same purpose for other or arbitrary pairs.

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