Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RUNE

Paid. THORChain (RUNE) 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/RUNE.

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

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 present, the description carries the full burden and does much of it: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted chains (Base or Solana), that no auth is required, and that failures are not charged — meaningful commercial behavior an agent cannot get from structured fields. It stops short of stating latency, rate limits, or freshness guarantees for a 'live' price.

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.' so cost is known before anything else, then purpose, then payment rails, then the endpoint. It is dense and nearly waste-free; the raw URL is of marginal value to an agent but still short enough not to bloat the definition.

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, no-output-schema tool, it covers the essentials: what data comes back, what it costs, where to pay, and that failures are free. The main residual gap is any statement about data freshness or failure modes beyond 'not charged'.

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 a parameterless single-asset call and adds no misleading parameter claims.

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?

Names a specific resource (THORChain / RUNE) and the exact payload: live USD price, 24h change, market-cap rank. That is far more than a restated name. It does not explain how it relates to the many sibling price tools (buy_coin_*, buy_crypto_price), so an agent must infer the distinction.

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?

Gives operational context (no account, no API key, failed calls not charged) and the payment requirement, which implicitly says 'use only if you can pay'. However, it never states when to pick this over the numerous alternative price tools in the sibling list, nor any exclusions.

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