Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BNB

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description takes on most of the disclosure burden, and it covers the paid model, the exact price, the auth-free access, the failure-not-charged policy, and the data sources with a Kraken cross-check. It does not explain the payment mechanism or the response shape, but the behavioral core is unusually well covered for a no-annotation tool.

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 description is short and front-loads the paid status and the returned fields. The telegraphic fragments are dense but readable, and every clause adds value, with no padding.

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 and no annotations, the description compensates by listing the returned fields, the data sources, and the payment terms. Only the choice of this tool over buy_crypto_price is missing.

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?

It takes zero parameters, and the schema is empty, so a baseline 4 applies. There is no parameter meaning to add or omit.

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?

It states a specific verb-and-resource: live BNB/USD price with last price, 24h OHLC, % change, and 24h/30d volume. The ticker in the name and description makes it distinct from the other buy_coin_* siblings. It stops short of explicitly saying that it is the BNB-specific instance rather than an aggregation tool.

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 gives clear payment prerequisites: $0.10 USDC on Base, no account, and no API key. It does not say when to prefer it over buy_crypto_price or explain how it relates to the other per-coin sibling tools. That leaves the agent to infer usage from the ticker name.

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