Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TRUMP

Paid. TRUMP/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/TRUMP.

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

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 to lean on, the description still discloses the key behavioral facts: it costs $0.25 USDC on Base, requires no account or API key, failed calls are not charged, and data is sourced from Coinbase Exchange with a Kraken cross-check. Rate limits, latency, and success/failure response shape are not stated, 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?

Front-loaded with the billing flag ('Paid') and then the payload, cost, and access terms in tight telegraphic sentences. Every clause carries information, though the raw endpoint URL is arguably filler for an agent that cannot call it directly.

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 paid fetch with no output schema, the description enumerates the returned fields, the payment rail and price, and the failure-billing policy, which is what an agent needs before spending money. Only the response format (JSON shape, units, timestamps) remains implicit.

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 add; this earns the baseline 4. The description correctly avoids inventing parameter guidance and instead spends its words on payment and data semantics.

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 data payload: TRC-USD/USD last price, 24h OHLC, % change, and 24h/30d volume for TRUMP. It implicitly corrects the misleading 'buy_coin' name by revealing this is a paid data fetch, not a coin purchase. It does not explicitly differentiate itself from the generic sibling buy_crypto_price, which is the only gap.

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?

The prerequisites ('No account, no API key') imply this is a self-serve paid fetch, and the ticker in the name implies the TRUMP-specific use case. However, with 300+ sibling coin tools plus buy_crypto_price and buy_pm_trump, the description gives no explicit guidance on when to pick this over those alternatives.

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