Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BNCB

Paid. CEA Industries (bStocks Tokenized Stock) (BNCB) 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/BNCB.

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

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 provided, the description must carry the full behavioral burden, and it does disclose important traits: cost ($0.01 USDC on Base or Solana), no account or API key required, and that failed calls are not charged. It stops short of covering rate limits, response freshness/latency, whether payment is settled per call or per session, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, leading with the paid nature and the asset identity before cost and access terms. The sentence-fragment style packs several facts into one line without filler, though the trailing raw URL is somewhat abrupt and the 'Paid.' opener is slightly redundant with the later pricing sentence.

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, single-asset price lookup with no output schema, the description covers the essentials an agent needs: what data is returned, what it costs, which chains are supported, and that no credentials are needed. The absence of an output schema is offset by the description naming the returned fields, leaving only minor gaps around error/payment behavior.

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 (empty schema), so there is no parameter semantics to document and no risk of ambiguity. The description correctly spends its words on the fixed asset identity and returned fields rather than inventing input details.

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 the specific asset (CEA Industries bStocks Tokenized Stock, ticker BNCB) and states exactly what the endpoint returns: live USD price, 24h change, and market-cap rank. This clearly distinguishes the tool's payload from sibling buy_tok_* endpoints, though it never explicitly contrasts itself with the buy_coin_* or buy_stable_* families or explains when the 'tok' variant should be chosen over 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?

Usage is implied by the price-data payload and the 'Paid' marker, so an agent can infer when to call it. However, there is no explicit when-to-use guidance, no mention of alternatives or fallbacks for obtaining BNCB pricing, and no stated conditions under which this specific endpoint should be preferred.

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