Skip to main content
Glama

SouthPow crypto & market data

buy_stable_ausd

Paid. Agora Dollar (AUSD) 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/ausd.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full disclosure burden and does well on cost, chain options, authentication, and failure billing. It omits the response format and, more importantly, how payment is actually executed (automatic per call vs. pre-funded balance), which matters for a paid tool.

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

Conciseness3/5

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

The opening 'Paid.' front-loads the most decision-relevant fact, and the data fields are listed compactly. However, the sentence is a dense run-on mixing data contents, pricing, chains, auth policy, and a raw URL, so the agent has to parse a lot to extract what matters.

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 fetch with no output schema, the description enumerates the returned fields and names the upstream source (DefiLlama), plus the endpoint URL. That is close to complete; the only real gap is the mechanics of paying for the call.

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 beyond what the schema provides; baseline 4 applies.

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 a concrete resource (Agora Dollar / AUSD stablecoin data) and enumerates exactly what comes back: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply. The 'buy' verb is resolved as purchasing paid access to that data. It is unambiguous what this returns, though the sibling differentiation comes from the tool name rather than any comparative 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?

It tells the agent the call is paid ($0.01 USDC on Base or Solana), needs no account or API key, and that failed calls are free, which is practical usage context. It never says when to prefer this over a sibling such as buy_yields_stablecoins or buy_crypto_price, so the agent must infer selection from the coin-specific name.

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