Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BOB

Paid. BOB (Build on Bitcoin) (BOB) 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/BOB.

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

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 provided, the description carries the full load and does so reasonably well: it discloses that the call is paid, the exact price and payment chains, that no account or API key is required, that failed calls are not charged, and what data the response contains. It omits rate limits and any delivery/refund mechanics, which keeps it short of a 5.

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?

The description is short and front-loads the key fact (paid) followed by what is returned and how to pay. There is minor redundancy in 'BOB (Build on Bitcoin) (BOB)', where the ticker appears twice, but otherwise every sentence carries information.

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 price lookup with no output schema, the description supplies enough to call the tool correctly: it names the returned fields, the cost, payment options, and the endpoint. Only secondary details such as freshness/rate limits are absent, which are minor for this complexity.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent parameters, instead spending its space on payment and output context.

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 and action: the live BOB (Build on Bitcoin) token price with 24h change and market-cap rank. It even expands the ticker, so an agent cannot confuse it with an unrelated token. It does not explicitly contrast itself with the many sibling token/price tools (e.g., buy_coin_BOBBOB or buy_crypto_price), which keeps it below 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?

It gives purchase mechanics ($0.05 USDC on Base or Solana, no account, no API key) and confirms failed calls are free, which implies when this tool is practical. However, it never states when to choose this over the dozens of sibling price/coin tools, so routing guidance is only implied.

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