Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RNT

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

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

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 must carry the full behavioral burden, and it does a solid job: paid operation, exact price and payment chains (Base or Solana), no auth required, and a no-charge-on-failure policy. It does not mention freshness/latency or rate limits, which are the remaining gaps 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Seven short fragments, no filler, with cost and payment terms up front. The telegraphic style ('Paid.', 'No account, no API key.') is efficient, though the trailing raw URL is vendor detail the agent cannot act on.

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-output-schema tool, the description covers what data comes back, what it costs, how to pay, and the failure policy — enough to invoke it correctly. Only the absence of freshness expectations and rate-limit behavior keeps it from full marks.

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 schema has zero parameters, so there is nothing to disambiguate. The description usefully confirms the no-argument model by stating no account or API key is needed, matching the empty required list.

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 specific resource and payload: RNT's live USD price, 24h change and market-cap rank. It clearly differs from non-token siblings like buy_fx_eur or buy_tvl_base, but it never distinguishes itself from buy_coin_RNT or buy_crypto_price, which likely serve overlapping price data.

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 guidance is commercial rather than functional: it states the $0.01 USDC cost on Base or Solana, that no account or API key is required, and that failed calls are not charged. It never says when to pick this over the many sibling price tools, so the agent must infer selection from the ticker alone.

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