Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WBX

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

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

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, the description carries the behavioral burden well: it discloses that the call is paid ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits, data freshness/refresh cadence, and the response format, which are meaningful gaps for a paid data endpoint.

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?

Extremely tight: payment model is front-loaded in a single word ('Paid.'), followed by the payload contents, cost/auth details, and the endpoint. Every sentence adds information and none repeats structured data.

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 purpose, cost, payment rails, auth requirements, billing-on-failure, and the URL. The only missing piece an agent would want is what the response body looks like, since there is no output schema to fall back on.

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 schema has zero properties, so there is nothing for the description to clarify beyond confirming the call takes no arguments. Baseline of 4 applies; the description appropriately does not waste space re-describing an empty input.

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 resource precisely ('Wibx (WBX) price') and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. It distinguishes itself from the many sibling buy_tok_* tools by identifying the token, though it never states its relationship to generic siblings like buy_crypto_price.

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?

Usage is implied by the token-specific name and the price fields listed, and 'Paid. ... $0.05 USDC on Base or Solana' signals the cost context before calling. There is no explicit when-to-use guidance, no exclusion, and no pointer to an alternative such as buy_crypto_price if a different token or multi-asset quote is needed.

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