Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BR

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

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

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 cost, accepted payment (USDC on Base or Solana), that no authentication is required, that failed calls are not billed, and the underlying endpoint URL. What is missing is how the payment is actually transacted (prepay, x402 header, etc.) and any rate or freshness limits.

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?

Three short sentences, front-loaded with the paid flag, then the payload, then the commercial terms. Every clause carries distinct information with no repetition.

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 read endpoint with no output schema and no annotations, the description covers what is returned, cost, payment rails, auth posture, and failure billing. The main gap is the mechanics of paying and receiving the response, plus any fallback when the call fails.

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 defines zero parameters, so the baseline is 4. There are no parameters whose meaning could be clarified, and the description correctly implies the token is fixed by the tool rather than passed in.

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 specific resource (Bedrock/BR) and enumerates what it returns: live USD price, 24h change, and market-cap rank. An agent can tell this from a generic price tool by the token symbol. However, it never mentions the large buy_tok_* family or sibling buy_crypto_price, so sibling differentiation is left implicit.

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 gives decision-relevant facts for using it (it is paid, costs $0.05 USDC, needs no account or API key, failed calls are free), which implies usage but does not state it. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to an alternative such as buy_crypto_price if the agent wants a different or broader price feed.

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