Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BONK

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

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

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 burden and does well: it discloses that the call is paid, the exact price ($0.10 USDC on Base), the payment chain, that no account or API key is needed, and that failed calls are not charged — the key risk facts for a metered call. It stops short of explaining how payment is actually settled (wallet/x402 flow) or expected latency.

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?

Extremely dense but front-loaded: 'Paid.' leads, then payload, then price/chain, then access terms, then endpoint. Every clause carries information an agent needs and there is no filler.

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?

With no output schema, the description must describe return values and it does — enumerating the price fields, change, and volume windows plus their provenance. The payment mechanics are the only material gap for a paid tool, but the endpoint URL and cost are given so an agent can proceed.

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 adds no parameter prose, keeping the ticker baked into the name.

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 a specific resource and payload: BONK/USD last price, 24h open/high/low, % change, and 24h/30d volume, plus the data sources (Coinbase Exchange with Kraken cross-check). An agent can tell exactly what it gets back. It does not explicitly contrast itself with the ticker siblings or with buy_crypto_price, relying on the tool name for that differentiation.

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?

Provides cost and access context ('$0.10 USDC on Base. No account, no API key. Failed calls not charged.') which is genuinely useful for deciding whether to call at all. However, it never states when to prefer this over buy_crypto_price or the other buy_coin_* ticker tools, nor any when-not condition.

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