Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RNBW

Paid. RNBW/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/RNBW.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 a solid job: it discloses that calls are paid, the exact price and payment chain, that no account or API key is needed, and that failed calls are not charged — all non-obvious operational facts. It still omits how payment is actually settled on the call (e.g., payment header/protocol) and whether data is real-time or delayed.

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 a tight, telegraphic block that front-loads the most decision-relevant fact ('Paid.') and then enumerates the returned fields, cost, access, and URL with no filler. The sentence fragments read as terse but every clause carries information; only the trailing raw URL feels appended rather than integrated.

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?

With no output schema, the description must convey what comes back, and it does by enumerating the price fields and the source venues. Combined with the cost, payment, and failure-charge policy, an agent can decide and call correctly. The remaining gap is response format and latency/freshness, which is minor for a zero-parameter read endpoint.

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?

There are zero input parameters, so the baseline is 4. The description handles this correctly by supplying the endpoint URL, making clear the symbol is baked into the path rather than passed as an argument. Nothing about parameters is left ambiguous.

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 and payload: RNBW/USD live price with last price, 24h open/high/low, percent change, and 24h/30d volume, plus the source venues (Coinbase Exchange with Kraken cross-check). The tool name says 'buy_coin' while the payload is a price feed, but the description corrects that immediately. It is clearly the RNBW instance of the buy_coin_* family, though it never explicitly routes to sibling symbols.

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 gives access conditions ('No account, no API key') and cost framing ('$0.002 USDC on Base'), which implicitly tells the agent this is callable without setup. However, it never states when to prefer this over alternatives such as buy_crypto_price, nor any exclusion or preconditions for the paid path. Usage is implied rather than prescribed.

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