Skip to main content
Glama

SouthPow crypto & market data

buy_tok_QRL

Paid. Quantum Resistant Ledger (QRL) 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/QRL.

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

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 and does well: it discloses payment ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — the key risk concerns for a paid endpoint. It stops short of explaining how payment is executed, rate limits, or latency, which keeps it from a 5.

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?

Four compact sentences, front-loaded with the decisive 'Paid' qualifier, then the data scope, then cost/auth/failure terms, then the endpoint URL. Every sentence supplies call-relevant information with no filler.

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-param paid lookup with no output schema and no annotations, the description covers cost, auth requirements, failure billing, returned fields and the underlying URL. It leaves open the payment mechanics and response shape details, but is sufficient to decide and invoke correctly.

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 the baseline is 4 and the description correctly adds no parameter discussion. Nothing is missing because there is nothing to specify.

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 (Quantum Resistant Ledger / QRL price) and enumerates what is returned: live USD price, 24h change and market-cap rank. It is clearly a single-asset price lookup, but it never distinguishes itself from the buy_coin_* or buy_crypto_price families that appear to offer overlapping price data, leaving the agent to guess which family to pick.

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?

Usage context is only implied: the 'Paid' prefix and the $0.05 USDC pricing indicate this is for agents that need QRL price data and are willing to pay. It gives no explicit when-to-use vs. when-not or alternative tool (e.g. buy_coin_QNT-style siblings), so selection guidance is weak.

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