Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BNT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 behavioral burden and does disclose the important traits: cost ($0.002 USDC on Base), no authentication required, and no charge on failed calls. It does not cover rate limits, latency, caching freshness of 'live' data, or what a failure response looks like.

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 and front-loaded: cost, then payload, then pricing/auth/error terms, then endpoint. Nearly every phrase carries information an agent would otherwise have to guess, and none of the sentences are 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?

For a zero-parameter read endpoint with no output schema, the description supplies the return-field list, cost, auth model, and error billing policy, which is close to sufficient. Only rate limits and response format/size are absent.

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 is 4; there is nothing for the description to disambiguate. The URL it includes at least hints at the underlying endpoint shape, though that is not needed for invocation.

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 verb-and-resource combination with the exact data returned (last price, 24h open/high/low, % change, 24h and 30d volume) and names the sources (Coinbase Exchange with Kraken cross-check). The ticker in the tool name plus BNT/USD in the description makes it trivially distinguishable from the ~400 sibling buy_coin_* tools.

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 prerequisites ('No account, no API key') and a failure policy, which implies usage context, but never says when to prefer this over the generic sibling buy_crypto_price or how it compares to other per-ticker endpoints. No exclusions or alternatives are named, so routing is left to inference from the ticker.

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