Skip to main content
Glama

SouthPow crypto & market data

buy_stable_rlusd

Paid. Ripple USD (RLUSD) stablecoin live: price vs peg, supply, 1d/7d/30d supply change, supply per chain (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/stablecoins/rlusd.

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

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?

No annotations are supplied, so the description carries the full burden, and it does disclose the traits an agent most needs: it is a paid operation with an explicit price and payment chains, requires no auth, and failed calls are not charged. That last point meaningfully de-risks invocation. It does not describe latency, rate limits, or the response shape, but the core behavioral contract is stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Front-loads the single most important fact ('Paid.') before anything else, then packs payload contents, price, payment rails, auth posture, failure policy, and endpoint into a few dense lines. No filler sentences; every clause carries decision-relevant information.

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 parameters and no output schema, the description compensates by enumerating the data fields returned, which is exactly what an agent needs to judge fit. Cost, payment chain, and failure billing are also covered. What remains unstated is the response format and any freshness/cadence guarantees, a minor gap for a fixed zero-arg 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level detail is needed or missing.

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?

Names the exact resource (Ripple USD / RLUSD stablecoin) and enumerates the specific metrics returned: price vs peg, supply, 1d/7d/30d supply change, and supply per chain, attributing the source as DefiLlama. Against the very large sibling set of buy_stable_* tools, an agent can tell instantly this is the RLUSD-specific endpoint rather than the USDC/USDT/DAI ones.

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 commercial terms (paid, $0.01 USDC on Base or Solana, no account/API key, failed calls not charged) tell the agent the preconditions for calling, which is useful gating. However, it gives no guidance on when to prefer this over siblings such as buy_yields_stablecoins, buy_cp_stablecoins-check, or a general crypto-price tool — no exclusions or alternative routing.

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