Skip to main content
Glama

SouthPow crypto & market data

buy_stable_cash

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 so well: it discloses cost and accepted payment chains, that no account or API key is needed, that failed calls are not billed, and the upstream data source (DefiLlama). Gaps remain around rate limits, data freshness/latency, and the mechanics of how the per-call USDC payment is actually settled.

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?

It is a short, telegraphic block with zero filler, front-loading the payment flag and the ticker before the payload contents and commercial terms. Each clause (data fields, price, auth, billing on failure, endpoint) carries distinct 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 output schema, the description compensates by listing the exact metrics returned, and it covers cost and access requirements, which is most of what an agent needs. The missing piece is the payment protocol itself (how USDC is remitted per call), which is material for a tool whose first word is 'Paid.'

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 per the baseline this scores 4. The description correctly adds no parameter detail, since there is nothing for an agent to supply beyond the call itself.

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 asset (CASH) and enumerates the returned metrics: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply. It is clearly distinguishable from the many buy_stable_* siblings by ticker, but the retrieving verb is only implied ('live'), so it falls just short of a full verb+resource statement.

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?

Pricing ($0.002 USDC on Base or Solana), the no-account/no-key requirement, and the no-charge-on-failure policy tell an agent when this call is viable, which is useful. However, there is no explicit guidance on when to pick this over adjacent tools such as buy_crypto_price, buy_cp_stablecoins-check, or buy_yields_stablecoins, so routing is left to inference from the ticker.

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