Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BRLV

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

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

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 reasonably well: it discloses the paid cost and payment rails, that no auth is required, and the billing policy ('Failed calls not charged'). What it omits is the success/return shape and any rate limit or idempotency behaviour, so it is strong but not complete.

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?

It is short and front-loaded, leading with 'Paid' and the price before the payload and the endpoint. The telegraphic sentence fragments are efficient but slightly clipped; every clause still contributes information.

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 no-parameter, no-output-schema paid endpoint this covers what an agent needs to decide and invoke: which asset, what data, the cost, the chains, the auth requirement, and the failure-charge policy. A brief note on return format or response latency would close the remaining gap.

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, which is the baseline-4 case. The description correctly reflects that nothing is configurable and that the asset is fixed in the tool name and URL rather than passed as an argument.

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 concrete resource and payload: 'Crown BRLV (BRLV) price: live USD price, 24h change and market-cap rank.' An agent can tell exactly what data comes back. It does not distinguish itself from near-neighbours such as buy_crypto_price or the buy_coin_* family, so it stops short of a 5.

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?

Preconditions are stated implicitly through 'Paid ... $0.05 USDC on Base or Solana' and 'No account, no API key', which tells the agent what is needed to call it. There is no explicit when-to-use versus alternatives guidance, and no mention of when not to call it or of a cheaper sibling for the same data.

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