Skip to main content
Glama

SouthPow crypto & market data

buy_tok_B2

Paid. BSquared Network (B2) 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/B2.

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

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, the description carries the full burden, and it does disclose useful billing behavior: paid, $0.05 USDC on Base or Solana, no account or API key required, and failed calls are not charged. It stops short of explaining how payment is attached to a zero-parameter call (e.g., x402 flow), any rate limits, or the response payload shape.

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?

Three short, front-loaded sentences with the payload described first and cost/payment details after. The raw endpoint URL is arguably filler for an agent, but nothing is duplicated or bloated.

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 parameterless paid endpoint with no annotations and no output schema, the description covers the returned fields, the price, the payment rails, the no-auth model, and the failure-charging policy. What remains missing is modest: rate limits and the concrete response format.

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 there is nothing for the description to clarify beyond the schema. Baseline 4 applies; the description correctly avoids inventing parameter guidance for a parameterless endpoint.

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 states a specific resource and payload: 'BSquared Network (B2) price: live USD price, 24h change and market-cap rank', which is far more than a restatement of the name. It differentiates itself from the huge buy_coin_/buy_tok_ sibling set by explicitly naming the asset and the exact fields returned, though it does not name a sibling alternative directly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no pointer to an alternative (e.g., a free or broader price endpoint). The only decision-relevant context is indirect: the tool is paid at $0.05, which implies an agent should only call it when the B2 quote is actually needed.

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