Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RLC

Paid. RLC/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.10 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/RLC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose useful behavior: it is paid ($0.10 USDC on Base), requires no account or API key, failed calls are not charged, and sources are Coinbase Exchange with a Kraken cross-check. It does not state the transport (GET/POST), response format, latency, or what a failed call looks like, so the payment/cost picture is clear but the mechanics are not.

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 dense and front-loaded, opening with 'Paid.' so the cost signal is immediate, followed by the data payload, price, access requirements, and URL. The telegraphic fragment style is efficient, though slightly terse where a short clause would read better.

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 tool with no output schema, the description compensates by enumerating the returned fields and the payment/access model, which is what an agent needs to decide and call. Remaining gaps are the response encoding and failure semantics, which are minor at this complexity.

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. The description correctly implies no input is required, and the coin is baked into the endpoint URL it quotes.

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 exact resource (RLC/USD) and enumerates the returned data points: last price, 24h open/high/low, % change, 24h and 30d volume. It is distinguishable from the hundreds of buy_coin_<SYMBOL> siblings by the coin symbol, though the name's 'buy_coin' prefix is not explained and could read as a trade action rather than a data purchase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus the generic buy_crypto_price sibling or versus a different buy_coin_<SYMBOL> tool. The only implicit guidance is that this endpoint is RLC-specific, leaving the agent to infer selection criteria.

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