Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WBT

Paid. WhiteBIT Coin (WBT) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/WBT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the important traits: it is a paid call ($0.01 USDC on Base or Solana), requires no auth, and failed calls are not charged. It omits rate limits, latency, and whether repeated calls are cached or billed each time, which matters for a paid endpoint.

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?

The paid/asset framing is front-loaded and every clause carries information — price, what fields are returned, cost, payment chains, auth, failure policy, endpoint. The telegraphic style ('Paid.'; 'URL https://...') is efficient but slightly choppy.

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 say what comes back, and it does (USD price, 24h change, market-cap rank). It also covers the commercial and auth model. The return shape is only a list of fields with no indication of format, nesting, or freshness, which keeps it from a 5.

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 of 4 applies. The description adds no parameter meaning beyond the input schema, and none is needed.

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 a specific verb and resource — 'WhiteBIT Coin (WBT) price: live USD price, 24h change and market-cap rank' — so an agent knows exactly what data comes back. It does not explicitly differentiate itself from generic siblings such as buy_crypto_price or the parallel buy_coin_* family, so it falls short of a 5.

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 practical context (paid, no account, no API key, failed calls not charged) that implies when this is usable, but never states when to prefer it over buy_crypto_price or another token tool. Usage must be inferred from the asset symbol alone.

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