Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RMSTU

Paid. T-Rex 2X Long MSTR Daily Target ETF Tokenized Stock (Reality) (RMSTU) 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/RMSTU.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses that the call is paid ($0.05 USDC), the accepted payment networks (Base or Solana), that no account/API key is needed, and that failed calls are not charged. Not covered: rate limits, latency, or what a failure/error response looks like, 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?

Sentences are short and front-loaded with the most decision-relevant fact ('Paid'), followed by payload, price, and access terms. The full ETF legal name is verbose but necessary to disambiguate RMSTU from sibling tokens; the redundant URL costs a little space.

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?

There is no output schema, and the description compensates by enumerating the three returned fields; with no input parameters the calling surface is fully covered, and payment/access mechanics are spelled out. It stops short of describing response shape or units for market-cap rank, which an agent would otherwise need.

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 and the baseline is 4. The description correctly implies the asset and payment rail are baked into the endpoint (the URL confirms it) rather than being caller-supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource ('T-Rex 2X Long MSTR Daily Target ETF Tokenized Stock ... (RMSTU)') and the exact payload returned ('live USD price, 24h change and market-cap rank'). Against a sibling list of hundreds of near-identical buy_tok_* tools, this identifies the single asset and the payload, so an agent can select it without opening the schema.

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: this is the paid price lookup for RMSTU specifically. But it never states when to prefer it over a sibling (e.g. buy_crypto_price or buy_coin_MSTR-adjacent tools) or when not to use it, and there is no guidance on caching or repeat calls despite a per-call cost.

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