Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TUSD

Paid. TrueUSD (TUSD) 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/TUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the key traits: it is a paid operation, the exact price and accepted payment rails, that no credential is required, that failures are not billed, and the backing URL. It does not describe the shape of the returned payload or latency/rate-limit behavior, keeping it short of 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?

The description is short and front-loads the most decision-relevant fact ('Paid.'), then cost and data content. It is written as a terse fragment list rather than prose, which is efficient but slightly harder to parse for the payment mechanics.

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 paid price feed, the description covers what is returned, what it costs, on which chains, and that no auth is needed. The main omission is how payment is actually settled during the call, which an agent invoking a paid endpoint would benefit from knowing.

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. Nothing in the description needs to explain argument meaning, and the target asset is fixed in the tool name and description.

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 resource specifically ('TrueUSD (TUSD) price') and enumerates the returned fields: live USD price, 24h change, and market-cap rank. It does not distinguish itself from the many near-identical siblings, notably buy_stable_tusd and the buy_coin_* family, so an agent cannot tell which TUSD variant to pick from the description 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?

Purchase context is stated clearly (paid, $0.01 USDC on Base or Solana, no account or API key, failed calls not charged), which tells the agent how to transact. However, there is no explicit when-to-use guidance and no mention of the alternative TUSD-related tools that a caller would need to compare against.

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