Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BIC

Paid. Beincom (BIC) 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/BIC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/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 add real value: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It does not cover rate limits, latency, or what an error/empty response looks like, so the behavioral picture is useful but incomplete.

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-loaded with "Paid." then the payload, then cost/payment terms, then the endpoint. Nearly every clause earns its place; the raw URL at the end is the only element of questionable value to an agent that invokes by tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 lookup, the description covers what is returned, what it costs, how to pay, auth requirements, and failure billing. Nothing further is needed to call it correctly.

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 no parameters, so the baseline is 4; the description correctly introduces no parameter semantics and instead spends its words on cost and payload, which is the right allocation.

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 and payload: "Beincom (BIC) price: live USD price, 24h change and market-cap rank." That is a concrete verb+resource, and naming the token and ticker differentiates it from the hundreds of buy_tok_* siblings. It stops short of calling out a sibling alternative (e.g. buy_crypto_price), so it is clear but not fully differentiated.

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?

The "Paid. $0.05 USDC..." framing implies this is a purchasable single-token lookup, and "Failed calls not charged" tells the agent retrying is safe, but there is no explicit when-to-use/when-not guidance or pointer to a cheaper general alternative such as buy_crypto_price.

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