Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RVN

Paid. Ravencoin (RVN) 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/RVN.

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

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 carries the full burden and does a solid job: it discloses the paid pricing model, the accepted payment chains, the zero-auth requirement, the failure-billing policy, and the backing endpoint. It omits data freshness/update cadence and rate limits, which matter for a price feed, 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?

Terse and front-loaded: paid status and result contents lead, then cost, then operational caveats, then the URL. The sentence fragments are dense rather than wasteful, though the bare URL and 'Paid.' opener read as terse shorthand rather than polished prose.

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 price lookup, the description supplies the returned fields, the payment mechanics, auth requirements, and failure policy — enough for an agent to call it correctly. The remaining gap is non-disclosure of response format and refresh cadence.

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 the baseline is 4. The description correctly spends no words on parameters and instead describes what the fixed call returns.

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 gives a specific verb+resource: 'Ravencoin (RVN) price: live USD price, 24h change and market-cap rank.' It even enumerates the three fields returned, so an agent knows exactly what it gets. It does not, however, distinguish itself from the very similarly named sibling buy_coin_RVN, which appears to cover the same asset.

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 description explains cost ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — useful preconditions for committing to a paid call. What it never states is when to pick this over buy_coin_RVN or buy_crypto_price, nor any exclusion criteria, so the usage decision is only implied.

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