Skip to main content
Glama

SouthPow crypto & market data

buy_stable_usdt

Paid. Tether (USDT) 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/usdt.

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

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 usefully discloses the $0.002 USDC charge, supported payment networks, lack of account or API-key requirements, and that failed calls are not charged. It also identifies the data source and live nature, though it does not explicitly state that the operation is read-only or discuss freshness, rate limits, or payment authorization mechanics.

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?

The description is compact and information-dense, with each fragment adding useful scope, pricing, authentication, failure-billing, or endpoint information. Leading with the paid status is reasonable for a purchased data call, and there is no substantive filler.

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-argument lookup without an output schema, enumerating the metrics and source alongside the commercial behavior covers most selection and invocation needs. It would be more complete with explicit read-only wording, response timing or units, and guidance distinguishing it from simpler price, stablecoin-overview, and yield alternatives.

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?

There are no parameters, so the zero-input baseline applies. The fixed USDT endpoint and asset-specific wording reinforce that no asset, date-range, or chain selector needs to be supplied.

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 identifies Tether (USDT) and precisely lists the live data provided: price versus peg, supply, 1d/7d/30d supply changes, and supply per chain, sourced from DefiLlama. It clearly conveys a data lookup rather than a token purchase, but does not explicitly differentiate it from price-only or other USDT-related siblings.

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?

An agent can infer that this tool is appropriate when USDT peg and supply analytics are needed. However, it gives no explicit when-to-use or when-not guidance and does not route simpler price requests to buy_crypto_price or yield requests to buy_yields_token_usdt.

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