Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TRUSD

Paid. Tori trUSD (TRUSD) 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/TRUSD.

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

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 carries the full behavioral burden and does a reasonable job: it discloses the monetary cost, the accepted payment assets and chains, that no account or API key is required, and the notable policy that "Failed calls not charged." What is missing is freshness/caching behavior of the quoted price and whether repeated calls in one session are re-billed, which matters 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, front-loaded with payment status and the returned data, followed by cost, access requirements, billing policy, and the endpoint URL. No filler, and each sentence carries a distinct fact an agent needs.

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-annotation, no-output-schema tool, the description covers the essentials: what is returned, what it costs, how to pay, and that failures are free. The gaps are the price data's freshness/staleness semantics and the response shape, which the absent output schema would otherwise have handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is an empty object with zero parameters, so the baseline of 4 applies for the schema itself. The description adds only contextual constraints (payment chain, cost) rather than parameter meaning, and there are no parameters to disambiguate. Score reflects that no meaningful semantic lift beyond the schema was needed or provided.

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 resource and payload: "Tori trUSD (TRUSD) price: live USD price, 24h change and market-cap rank." That distinguishes it from the other buy_tok_* siblings by symbol and tells the agent exactly what data comes back. It never uses a verb like "fetch" or "buy" in prose, relying on the name plus "Paid" and the $0.01 charge to convey the transactional nature, which is why it falls short of a 5.

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?

Prerequisites are stated clearly ("$0.01 USDC on Base or Solana", "No account, no API key"), which is genuinely useful gating information. However, there is no guidance on when to pick this over related tools such as buy_coin_* or buy_crypto_price, nor any exclusion or alternative routing. Usage is implied by the token symbol rather than explained.

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