Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BDX

Paid. Beldex (BDX) 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/BDX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 well: it discloses that the call is paid, the exact price ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. The one meaningful gap is the payment mechanics — it never says whether settlement is automatic (e.g. x402 handshake) or what happens if the wallet lacks funds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short fragments, each carrying distinct information: payment status, payload, price, auth requirement, failure policy, endpoint. Nothing is redundant and the most decision-relevant fact ('Paid') is front-loaded.

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 the returned fields, cost, auth model and failure billing, which is close to everything an agent needs to decide and invoke. Only the payment flow and any response-format detail are missing, which is a minor shortfall at 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 input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies a parameterless call by baking the asset symbol into the endpoint URL.

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: 'Beldex (BDX) price: live USD price, 24h change and market-cap rank', which tells an agent exactly what data comes back. The ticker in the tool name combined with the description separates it from the many sibling price tools. It does not, however, explain how this differs from neighbours like buy_crypto_price or the buy_coin_* family, so sibling differentiation is implicit rather than stated.

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 description supplies commercial preconditions (paid, $0.05 USDC, no account or API key) that imply when this tool is callable, but it never says when to prefer it over the alternative price tools in the catalog. There are no exclusions or routing hints, so an agent must infer selection from the ticker alone.

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