Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RARI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 behavioral burden and does a solid job: it discloses that the call is paid ($0.10 USDC on Base), that no credentials are required, and that failed calls are not charged — important commercial behavior an agent must know before invoking. It stops short of latency, rate limits, or what a failure response looks like.

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 the most decision-relevant fact ('Paid.') and packs payload, price, access terms, and endpoint into a few dense fragments with no filler. The telegraphic style is efficient, though the cost terms and access terms could be grouped more legibly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description must convey what comes back and on what terms — it enumerates the returned metrics, names the venues, and states the payment model and endpoint. Nothing essential to a correct invocation is missing.

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; there is no parameter semantics to add and the description correctly spends no words on inputs. The coin symbol is baked into the endpoint URL, which reinforces that no argument is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resource (RARI/USD live) and the specific fields returned — last price, 24h OHLC, % change, 24h and 30d volume — plus the data sources (Coinbase Exchange with Kraken cross-check). An agent can distinguish this from the ~400 other buy_coin_* siblings purely from the symbol and payload described, without opening the schema.

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?

Implicitly tells the agent this is the tool for RARI spot pricing, and clarifies access conditions (no account, no API key). However, it never addresses the more general sibling buy_crypto_price or says when to prefer one over the other, and gives no exclusions or freshness 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