Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BNX

Paid. BinaryX [OLD] (BNX) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/BNX.

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

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 carries the full burden and does disclose the important traits: it is a paid call, the exact price and settlement chains, no authentication required, and that failed calls are not charged. It does not state freshness/latency or response format (JSON shape), leaving minor gaps.

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?

Front-loaded with the key facts (paid, what data, fields) followed by cost, access model and endpoint. The telegraphic sentence fragments are dense but readable; the URL and payment chain detail each earn their place for an agent deciding whether to spend money.

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?

There is no output schema, and the description compensates by listing the three returned metrics. For a zero-parameter, single-asset price call, the cost and access model plus the returned fields cover nearly everything an agent needs; only response format details 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 schema baseline is 4 and there is nothing further the description could clarify about inputs. The URL is included but adds little semantic value beyond endpoint identification.

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 resource (BNX / BinaryX OLD spot price) and enumerates the returned fields: live USD price, 24h change and market-cap rank. It does not explain how this differs from the near-identical sibling buy_coin_BNX or from buy_crypto_price, which is the main ambiguity for an agent selecting between them.

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?

Payment terms ($0.05 USDC on Base or Solana, no account, no API key, failed calls not charged) give useful context for whether to call it, but there is no explicit when-to-use or when-not-to-use guidance versus the many sibling price tools. Usage is only implied by the 'Paid.' prefix.

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