Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RAD

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rail (USDC on Base), that no account or API key is required, and the failure policy ('Failed calls not charged'). It omits latency, rate limits, and caching/staleness behavior, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single tight block with the most decision-relevant fact ('Paid.') front-loaded, followed by payload, cost, prerequisites, and endpoint. Every clause carries information; the raw URL is the one element of marginal value to an agent that will call the tool through the MCP layer.

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?

There is no output schema and no annotations, so the description must convey both the payload and the commercial terms, and it does: it enumerates the returned fields and states cost, payment method, auth requirements, and failure charging. What is missing is the response encoding/shape and any freshness or rate-limit guarantee for the quoted numbers.

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 there is nothing for the description to disambiguate. The description correctly does not invent parameter discussion and instead spends its words on the data payload and payment terms.

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 and dataset: RAD/USD live price with last price, 24h open/high/low, % change, and 24h/30d volume, plus the upstream venues (Coinbase Exchange with Kraken cross-check). That is far more specific than the sibling names alone, which only encode the ticker. It does not differentiate itself from the general sibling buy_crypto_price, so it falls short of a 5.

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?

The leading 'Paid.' plus '$0.01 USDC on Base' and 'No account, no API key' tells an agent the cost and prerequisite before committing, which is genuine usage context. However, there is no statement of when to choose this over buy_crypto_price or any other price sibling, and no exclusions. Usage is therefore implied by the ticker rather than guided.

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