Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BMT

Paid. Bubblemaps (BMT) 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/BMT.

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

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 burden and does well: it discloses the price ($0.01 USDC), the accepted payment rails (Base or Solana), that no account/API key is required, that failures are not billed, and the endpoint URL. It does not explain the mechanics of how payment is settled within the call, which is the main remaining behavioral unknown.

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?

Six tight fragments, with the paid nature and cost front-loaded before the data description and the endpoint last. The telegraphic style ('Paid.', 'No account, no API key.') is efficient rather than sloppy, though a slightly more connective phrasing would read better without losing density.

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, the description covers cost, payment chain, failure billing, absence of auth, and the returned fields — essentially everything needed to invoke it correctly. Only the settlement flow and data freshness are left implicit.

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 (schema coverage 100%), so there is nothing for the description to disambiguate; the baseline applies. It correctly implies the token symbol is baked into the tool rather than passed as an argument.

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: 'Bubblemaps (BMT) price: live USD price, 24h change and market-cap rank,' so an agent knows exactly what data comes back. It does not, however, distinguish itself from the many sibling price tools (buy_coin_*, buy_crypto_price) or explain why this token has a dedicated buy_tok_ endpoint.

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?

Useful decision context is present — it is paid, costs $0.01 USDC, needs no account or API key, and failed calls are free — which helps an agent decide whether to spend. But there is no explicit guidance on when to choose this over the sibling coin-price tools or what the prerequisite balance is.

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