Skip to main content
Glama

SouthPow crypto & market data

buy_stable_usdtb

Paid. Ethena USDtb (USDTB) 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/usdtb.

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.002 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Not covered are the HTTP method, response format, latency, or rate limits, which keeps it from a 5.

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-loaded with the returned data fields, followed by payment terms and the endpoint URL. Every clause (price, payment rail, no-account, no-charge-on-failure) conveys actionable information with no 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 parameterless paid endpoint with no output schema, the description substitutes well by listing the returned metrics explicitly and stating cost and payment mechanics. What is missing is the invocation detail (HTTP method / request shape) and response encoding, so an agent knows what it gets but not fully how to call it.

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 parameter semantics are moot and the baseline of 4 applies. The description does not need to explain any input, and nothing misleading is said about inputs.

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?

The description names the specific asset (Ethena USDtb / USDTB) and enumerates exactly what the call returns: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply. That level of specificity lets an agent distinguish it from the hundreds of sibling buy_stable_* and buy_coin_* tools 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?

Usage context is implied by the asset name, and payment mechanics are stated, but there is no explicit when-to-use or when-not-to-use guidance versus alternatives such as buy_stable_usdc, buy_crypto_price, or buy_yields_stablecoins. The agent must infer that this is the dedicated paid data endpoint for USDTB.

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