Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RSR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 disclosure burden and does well on the costly details: it is a paid endpoint, costs $0.002 USDC on Base, requires no account or API key, and failed calls are not charged. What it omits is operational behavior such as rate limits, caching/refresh cadence, and how the Kraken cross-check is reconciled.

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?

Front-loads 'Paid.' then delivers the data payload, cost, and access requirements in a tight telegraphic block with no filler. The raw URL at the end is marginally useful but slightly untidy; the dense fragment style is efficient rather than confusing.

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 price endpoint, the description supplies the returned field set, the underlying venues, payment terms, and the endpoint URL — enough for an agent to decide and call correctly. It stops short of describing the response structure or freshness guarantees, which would matter for a pricing 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 parameter semantics to be missing; the description correctly implies the call needs no arguments by advertising that no account or API key is required. Baseline for a zero-parameter schema applies.

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 concrete resource (RSR/USD live price) and enumerates the exact fields returned: last price, 24h open/high/low, % change, and 24h/30d volume. It is distinguishable from the hundreds of sibling buy_coin_<TICKER> tools by ticker and by the field list, though the 'buy_coin_' name implies a trade action that the description never reconciles with what is actually a read-only price feed.

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?

It says nothing about when to pick this over buy_crypto_price (a likely aggregated alternative) or whether it should be preferred over the 24h/30d volume sources cited. The only usage-adjacent information is commercial ('No account, no API key'), not selection guidance.

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