Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BBT

Paid. BabyBoomToken (BBT) 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/BBT.

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

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 supplied, the description carries the full burden and does a genuinely good job on the commercial behavior: it states the call is paid, the exact price ($0.01 USDC), the two accepted payment chains (Base, Solana), that no account or API key is needed, and critically that failed calls are not charged. The remaining gap is operational behavior — data freshness/latency, rate limits, and response format are not stated.

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 definition is front-loaded and dense: payment status first, then contents, then cost/chains, then billing policy, then URL. Nearly every clause carries decision-relevant information. The bare URL sentence is the weakest element, though it is plausibly needed for payment routing; a slightly tighter phrasing would remove it.

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, no-annotation paid endpoint, the description covers what an agent needs to decide and pay: what comes back, what it costs, where to pay, and that failures are free. It falls short only on freshness and response shape, which matter less here because there is no input to get wrong.

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 also correctly implies there is nothing to configure: the token and endpoint are baked into the tool.

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 exact resource (BabyBoomToken / BBT) and the exact payload: live USD price, 24h change and market-cap rank. An agent can tell this is a price-fetch tool and not an audit, FX or TVL tool. It does not, however, distinguish itself from the closely related buy_insider_BBT or the generic buy_crypto_price sibling, so an agent must infer the difference from the name prefix alone.

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 only implied: by naming price/24h change/market-cap rank it signals 'use this when you need BBT market data.' It gives no explicit when-to-use versus buy_insider_BBT or buy_crypto_price, and no exclusions. The purchase mechanics (cost, chains, no account) are guidance about paying, not about tool selection.

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