Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RIVER

Paid. River (RIVER) 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/RIVER.

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

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 carries the full disclosure burden and does well: it flags the tool as paid, quantifies the cost, names the accepted payment chains, and notes that failed calls are not charged — a meaningful billing guarantee. The gap is that it never explains how payment is transacted without an account or key, nor what a failure looks like to the caller.

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?

It is telegraphic and front-loaded: 'Paid.' and the cost come before the payload description, and every fragment (payment rails, auth posture, refund policy, URL) carries distinct information with no filler.

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 endpoint, the description covers the essentials an agent needs: what comes back, what it costs, how to pay, and that failures are free. What is missing is any hint of response shape or field types, which the absent output schema would otherwise have supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 semantics to add and the baseline is 4; however, the description supplies no invocation details either. It does at least pin the underlying resource path, which helps an agent reason about what the call targets.

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 the asset and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank, which is more specific than the bare tool name. It does not, however, differentiate itself from sibling endpoints such as buy_coin_RIVER or buy_crypto_price that likely return 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?

Prerequisites and mechanics are stated ('Paid', '$0.01 USDC on Base or Solana', 'No account, no API key'), which tells the agent it can call this without setup. But there is no guidance on when to pick this over the many other price-shaped siblings (buy_coin_RIVER, buy_crypto_price), and no explicit statement of when not to use it.

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