Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BPX

Paid. Black Phoenix (BPX) 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/BPX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description still carries real behavioral weight: the price, the accepted payment assets and chains (USDC on Base or Solana), the absence of authentication, and the key policy that failed calls are not charged. What is not disclosed is anything about rate limits, latency, or the shape of the response payload.

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?

Front-loaded with the fact that this is a paid call, then purpose, then price/payment terms, then the endpoint URL. Every fragment earns its place and nothing is repeated.

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, single-value paid endpoint with no output schema, the definition covers cost, payment rails, auth, failure billing, and the target data fields. The remaining omission is how the response is structured and how latency/expiry is handled on a paid-per-call lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema has nothing to explain and the baseline of 4 would normally apply. However, the description offers no parameter meaning at all and also does not describe the output shape, so the free baseline is offset by the missing return-field detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and result set: Black Phoenix (BPX) price with live USD price, 24h change and market-cap rank. The ticker symbol in the name plus the spelled-out token name makes the target instrument unambiguous against the hundreds of buy_tok_* siblings.

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 makes the commercial terms clear (paid, $0.05 USDC, no account/API key), which implies the context of use, but never states when to call this versus a generic price tool such as the sibling buy_crypto_price, nor any exclusion or prerequisite beyond payment.

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