Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BUSD

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

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

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 a decent job: it discloses the price, the accepted payment chains, that no auth is needed, and that failed calls are not billed — behavior an agent cannot infer from the empty schema. It stops short of stating response shape, latency or freshness guarantees.

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?

Very short and front-loaded, leading with 'Paid.' and then the payload, price, payment terms and endpoint. The telegraphic style ('BUSD (BUSD) price') is slightly redundant, but no sentence is wasted.

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 purchase endpoint, the description covers what is sold, what it costs, how to pay, auth requirements and failure billing. Only return format and data-freshness details are missing, which are minor for this complexity level.

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 nothing to disambiguate and the baseline applies. Listing the returned data points is a reasonable substitute for parameter detail.

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 concrete deliverable: BUSD live USD price, 24h change and market-cap rank, with the 'buy_' prefix making clear it is a paid data purchase. It is clear what the tool returns, but it never distinguishes itself from the near-identical siblings buy_coin_BUSD and buy_stable_busd, which any agent choosing among hundreds of token tools will notice.

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?

It supplies practical preconditions — $0.05 USDC on Base or Solana, no account or API key, failed calls not charged — which tells the agent how to pay but not when to pick this over the coin/stable siblings that also cover BUSD. Usage is implied by the payload description rather than explicitly routed.

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