Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BRZ

Paid. Brazilian Digital (BRZ) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/BRZ.

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

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 at all, the description carries the full burden and does well: it discloses the payment model, the exact price, both accepted chains (Base or Solana), that no account or API key is needed, that failures are free, and the underlying URL. It stops short of stating latency, data freshness beyond 'live', or any rate limit.

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?

Five short fragments, each carrying distinct information: purpose, cost, payment rails, auth requirements, billing behavior, endpoint. Nothing is repeated and the payload description 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 everything an agent needs to decide and call: what data, what it costs, how to pay, and that failures are free. Slightly incomplete only in that freshness/caching semantics for 'live' and a versioning note on the v1 URL are absent.

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 schema already has 100% coverage. The description adds only that no account or key is required, which is useful invocation context rather than parameter semantics.

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 (Brazilian Digital / BRZ price) and enumerates exactly what comes back: live USD price, 24h change and market-cap rank. An agent can tell immediately this is a paid BRZ price lookup, though it never explains how it differs from the many sibling price tools like buy_coin_BRZ or 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?

'Paid' plus the $0.01 cost implicitly tells the agent to weigh cost before calling, and 'failed calls not charged' reduces the risk calculus. But there is no explicit when-to-use versus the dense family of overlapping pricing siblings (buy_coin_*, buy_crypto_price, buy_stable_*), so the agent must infer which endpoint to pick.

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