Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RLB

Paid. Rollbit Coin (RLB) 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/RLB.

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

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 full burden and does well: it discloses the paid cost, accepted payment chains, that no auth is required, and that failed calls are not charged — meaningful behavioral context an agent needs before paying. It stops short of describing the response shape or freshness/latency, leaving a small gap.

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?

Densely front-loaded: 'Paid' and the returned fields come first, followed by payment and pricing terms. Every clause (cost, chains, no key, no charge on failure) earns its place with no redundancy.

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 is nearly complete: it names the returned fields, the price, the payment rails, and the endpoint URL. Missing only response format/freshness details, which are minor for this tool.

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 schema semantics to explain; the baseline for a no-param tool is 4. The description correctly implies the ticker is baked into the endpoint rather than passed as input.

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 a specific resource (Rollbit Coin, RLB) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. It is clearly a single-asset price tool, though it doesn't explicitly distinguish itself from the hundreds of sibling buy_tok_* / buy_coin_* price tools beyond the ticker in the name.

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 supplies practical invocation context (paid, $0.05 USDC on Base or Solana, no account or API key, failed calls not charged) which tells the agent how to use it. It gives no explicit when-to-use-vs-alternative guidance, e.g. how it differs from buy_coin_* or buy_crypto_price, so usage is implied by the ticker rather than stated.

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