Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDD

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

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

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 at all, the description carries the full burden and does well: it discloses the paid cost, accepted payment rails, the no-auth requirement, and the billing policy on failures. This is exactly the kind of context an agent needs before spending money. It stops short of stating rate limits or latency, so it is not fully exhaustive.

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?

It is front-loaded with the critical fact ('Paid') and then packs cost, rails, auth, billing policy, and endpoint into a few short fragments. The one redundancy is 'USDD (USDD)', which repeats the symbol to no purpose, but the rest of the text earns its place.

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, annotation-free paid endpoint with no output schema, the description covers the three things an agent needs: what data it returns, what it costs, and how payment/auth works. The named return fields compensate for the absent output schema. Only return format details and rate limits are unaddressed.

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 no parameter meaning to explain and the baseline applies. The description correctly implies the ticker is fixed by the tool name and fully documents what the parameterless call returns.

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 a concrete resource and its payload: USDD live USD price, 24h change, and market-cap rank. That is enough for an agent to know exactly what data comes back. It does not, however, distinguish this token tool from the many sibling token/price tools (e.g. buy_coin_*, buy_stable_usdd), which share near-identical naming and output shape.

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?

It supplies the practical preconditions for calling: it is paid, costs $0.01 USDC on Base or Solana, needs no account or API key, and failures are not charged. What is missing is routing guidance — nothing says when to pick this versus buy_coin_*, buy_stable_usdd, or the generic buy_crypto_price.

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