Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BSB

Paid. Block Street (BSB) 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/BSB.

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

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 at all, the description carries the full load and covers the traits that actually matter for a paid endpoint: the price, the accepted payment chains, the absence of auth requirements, and the guarantee that failures are not billed. It does not state rate limits, latency, or what a successful payment flow looks like end to end, so it is strong but not complete.

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?

Roughly four short sentences, front-loaded with the 'Paid' flag so the cost signal lands before anything else. Every clause carries information — cost, chain, auth, billing on failure, endpoint. Slightly telegraphic style ('Paid. Block Street (BSB) price: ...') costs it a point on readability.

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, no-output-schema tool, an agent needs to know what it gets, what it pays, and what it must supply — the description covers all three. The only gap is the shape of the response payload, which is described by field name but not by format or units.

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 input schema is an empty object, so there are no parameters whose semantics need explaining and the baseline of 4 applies. The description correctly implies a zero-argument call by fixing the asset in the tool name and URL rather than leaving it to the caller.

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 resource concretely ('Block Street (BSB) price') and enumerates the returned fields: live USD price, 24h change, market-cap rank. Against ~1,000 sibling buy_tok_* tools, the embedded ticker and project name make the selection unambiguous. It stops just short of 5 because it never contrasts itself with the aggregate sibling buy_crypto_price.

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?

The prerequisites are explicit and useful — '$0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged.' — which tells an agent what it costs and what it needs before calling. What is missing is any when-to-use framing: no statement of when to prefer this over buy_crypto_price or buy_coin_BSB, and no exclusions.

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