Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BCE

Paid. bitcastle Token (BCE) 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/BCE.

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

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, the description carries the full burden and does well: it discloses that the call is paid, the exact cost and accepted chains, that no auth/account is needed, and critically that failed calls are not charged. It omits response envelope, latency/refresh cadence, and rate limits, which are the remaining behavioral gaps.

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 cost flag, then purpose, then access terms, then endpoint — a sensible order with no filler. The telegraphic fragments ('Paid.', bare URL) are efficient though slightly clipped for an agent parsing natural language.

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 paid lookup with no output schema, the description covers price, access economics, billing-on-failure, and the underlying endpoint. The main missing piece is what the successful response looks like beyond the three named fields (format, currency, timestamp).

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 the baseline is 4; there is nothing for the description to disambiguate. The token is hard-coded via the tool name and endpoint, which is consistent with the empty schema.

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 specific asset (bitcastle Token, BCE) and the exact payload it returns — live USD price, 24h change, market-cap rank — so the agent knows what it is buying. It does not explicitly state the boundary against the hundreds of sibling buy_tok_<SYMBOL> tools or the related buy_coin_* family, so token disambiguation rests on the name/title 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?

Payment and access mechanics ($0.05 USDC on Base or Solana, no account, no API key) imply when this tool is usable, but there is no explicit when-to-use/when-not guidance and no named alternative such as buy_crypto_price or buy_coin_BCE for a same-asset comparison.

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