Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RUJI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, yet the description carries the important behavioral facts itself: it is a paid call at $0.05 USDC payable on Base or Solana, requires no account or API key, and failed calls are not charged. A useful disclosure that goes well beyond the empty schema; only rate limits and latency/freshness of the quote are absent.

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 sentences, front-loaded with payment status and payload contents, then pricing, then access constraints, then the endpoint URL. No filler or repeated schema information.

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?

With no output schema, the description does list the returned fields (price, 24h change, market-cap rank), which is what an agent needs to decide the call is sufficient. It does not describe response shape, units, or data freshness, which is a modest but real gap for a paid data endpoint.

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 nothing for the description to clarify beyond confirming the call is fully self-contained (asset and endpoint are baked in). Baseline of 4 applies for a parameterless tool.

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?

States a specific resource (Rujira/RUJI USD price) and enumerates exactly what is returned: live USD price, 24h change, market-cap rank. Because each sibling is a per-asset variant (buy_tok_*, buy_coin_*), naming the asset explicitly is precisely the disambiguation an agent needs.

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?

Implies usage (call this when you need the RUJI price) and discloses the practical prerequisites of paying per call, but never states when to prefer it over the generic sibling buy_crypto_price or how it differs from buy_coin_* variants. Alternatives are left to inference.

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