Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDT

Paid. Tether (USDT) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/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_tok_USDT"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses that the call is paid, the exact price ($0.05 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It does not cover rate limits, caching/latency, or the response shape beyond field names, 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.

Conciseness4/5

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

Front-loaded with 'Paid.' then the payload, then cost, then access requirements, then URL — a sensible order with little waste. The bare URL as a final fragment is slightly cryptic, and 'Paid.' is terse enough to momentarily read as a status rather than a pricing notice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, no-output-schema tool, the description should fully define the returned fields; it names three (live price, 24h change, market-cap rank) but not their format, currency, or precision. Payment mechanics are well covered, but the agent still has to call blind about the exact response payload.

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; the baseline for a no-param tool is 4. The description correctly implies no inputs are needed by stating 'No account, no API key.'

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?

States a specific verb+resource pair implicitly through the URL and data list: it returns Tether (USDT) live USD price, 24h change and market-cap rank. It is clear what the tool does, but it never distinguishes itself from the numerous sibling token tools (buy_coin_USDT, buy_stable_usdt, buy_crypto_price), which a reader could easily confuse with it.

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 is implied by the payload it promises (live price, 24h change, market-cap rank), so an agent can infer 'use this when you need current USDT pricing.' There is no explicit when-not guidance and no mention of the alternatives in the huge buy_tok_*/buy_coin_* family, so selection between near-identical siblings is left to the tool 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