Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RIF

Paid. Rootstock Infrastructure Framework (RIF) 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/RIF.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description does real work: it declares the tool is paid, quotes the price ($0.01 USDC on Base or Solana), states no account or API key is needed, and that failed calls are not charged — the last point is exactly the kind of billing behavior an agent needs before spending. It stops short of describing the response shape or latency, but covers the risky parts.

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?

Front-loaded with what it returns, followed by price, payment rails, auth requirements, and billing guarantee in a tight sequence. Every clause carries information an agent needs before invoking a paid endpoint.

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 paid endpoint, the definition supplies the commercial terms, auth posture, and the fields returned, which is close to complete. The raw URL is the one inclusion of dubious value to an agent that only needs to call the tool.

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 schema imposes nothing to document and the baseline of 4 applies. The description correctly implies the ticker is fixed rather than a caller-supplied argument.

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?

States a specific resource (RIF / Rootstock Infrastructure Framework) and the exact payload (live USD price, 24h change, market-cap rank), which is concrete enough for an agent to match a request. It does not name how it differs from the large buy_coin_* family, which may return similar price data for other tickers, so sibling differentiation is only implicit.

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 by the resource name: call this when you need a RIF quote. There is no explicit when-to-use or when-not clause and no pointer to alternatives such as buy_crypto_price or a generic coin-price tool, which matters in a sibling set this dense.

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