Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDE

Paid. Ethena USDe (USDE) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/USDE.

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

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 at all, the description carries the full burden and does meaningful work: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no authentication is needed, and that failed calls are not charged — a genuinely useful retry-safety fact. It stops short of stating rate limits, latency, or the response encoding, which leaves some behavioral gaps for a paid endpoint.

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?

Five short fragments, zero filler, and the most decision-relevant fact ('Paid') is front-loaded before the payload description and pricing terms. Every clause conveys actionable information: what it returns, what it costs, where to pay, and the failure policy.

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, no-output-schema tool, the description adequately covers return contents (price, 24h change, market-cap rank), payment terms, and the literal endpoint URL. What is missing is the response shape/serialization and any indication of data freshness, which matters for a live price feed but is a minor gap given the tool's simplicity.

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 the baseline is 4 — there are no argument semantics to document and the description does not need to compensate. The asset is fixed in the endpoint URL rather than passed as an argument, which is stated plainly.

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 specific asset (Ethena USDe), the exact verb-implied resource (live USD price endpoint), and enumerates the returned fields: price, 24h change, and market-cap rank. It does not, however, distinguish itself from near-identical siblings such as buy_stable_usde or buy_yields_token_usde, so an agent must infer the difference from the name alone.

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?

Payment mechanics are stated clearly (cost, chains accepted, no account or API key, no charge on failure), which implicitly tells the agent this is the tool to call when it needs spot USDE pricing and is willing to pay. There is no explicit guidance on when to prefer this over buy_stable_usde, buy_yields_token_usde, or buy_crypto_price, so usage is implied rather than directed.

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