Skip to main content
Glama

SouthPow crypto & market data

buy_tok_B2M

Paid. Bit2Me (B2M) 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/B2M.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 most of it: it declares the tool is paid, prices it at $0.01 USDC, names accepted chains (Base or Solana), states no account or API key is needed, and promises failed calls are not charged. Remaining gaps are rate limits, latency guarantees for the 'live' claim, and error semantics beyond the no-charge promise.

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-loads the most decision-relevant word ('Paid.') and then packs purpose, cost, payment rails, auth requirements, and endpoint into a few short clauses with no filler. The telegraphic listicle style and raw URL are functional rather than elegant, but nothing is wasted.

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, one-shot price lookup with no output schema, the description covers what an agent must know before spending money: what data comes back, what it costs, how to pay, and that failures are free. It omits response shape and freshness/SLA details, which is a modest but real gap for a paid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 disambiguate. The coin is fixed in the tool name and endpoint, which is correct for this design, but no parameter-level meaning is added because none exists.

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?

States a specific resource (Bit2Me/B2M price) and enumerates the returned fields: live USD price, 24h change, market-cap rank. That is far more informative than the name alone, which only encodes the ticker. It does not explicitly contrast itself with the generic buy_crypto_price sibling, so it stops short of a 5.

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 rather than stated: an agent can infer it should buy this when it needs a live B2M quote. There is no explicit when-to-use, no exclusion, and no guidance on picking this over buy_crypto_price or the buy_coin_* family for the same asset.

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