Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BRLA

Paid. BRLA Digital BRLA (BRLA) 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/BRLA.

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

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 supplied, the description carries the full burden and does well: it discloses cost ($0.05 USDC), accepted payment chains (Base or Solana), zero auth requirements, and the failure policy ("Failed calls not charged"). It also names the fields returned. It stops short of rate limits, latency, or what a failure response looks like.

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-loads "Paid." so the agent knows a cost exists before anything else, then the payload, then access/payment terms, then the endpoint. Every clause carries actionable information, and the slight redundancy of "BRLA Digital BRLA (BRLA)" is minor.

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 price lookup with no output schema, the description supplies cost, payment rails, auth model, refund policy, returned fields, and the endpoint URL — nearly everything needed to call it correctly. Only secondary operational details (rate limits, response format) 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 no parameter meaning to add; the baseline for a 0-param schema applies. The description correctly offers no parameter guidance because none is needed.

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?

Names the exact resource (BRLA Digital / BRLA) and the payload it returns: live USD price, 24h change, and market-cap rank. That is a specific verb-implied resource + field list an agent can match to the symbol in the tool name. It does not explicitly differentiate itself from the hundreds of sibling buy_tok_* tools beyond the embedded ticker, which keeps it off 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?

Gives practical context for calling ("Paid", "$0.05 USDC on Base or Solana", "No account, no API key") but never states when an agent should pick this over alternatives such as buy_crypto_price or buy_tok_* variants. Usage is implied by the symbol rather than instructed.

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