Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RAIN

Paid. Rain (RAIN) 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/RAIN.

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

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 burden and does a good job: it discloses the paid model ($0.01 USDC), accepted rails (Base or Solana), that no account or API key is needed, and crucially that failed calls are not charged. This is exactly the risk information an agent needs before spending money. It omits rate limits, latency, and what a failure response looks like, which keeps it below 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?

Front-loaded and dense: the paid flag, the payload, the price, the rails, the auth model, the failure policy, then the URL. Every sentence earns its place. The telegraphic fragments ('Paid.', 'No account, no API key.') trade grammatical polish for scan speed, which suits this catalog.

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 endpoint, the description covers what is returned (live price, 24h change, rank), what it costs, and what happens on failure. Nothing an agent needs in order to call it correctly is missing. Rate limits and an explicit alternative for other tokens are the only unfilled gaps.

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 and the description has nothing extra to explain. The only semantics worth covering — cost, payment network — are addressed even though they are not schema fields.

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 the specific resource and payload: live USD price, 24h change and market-cap rank for RAIN. The verb is implicit in the noun phrase but the resource is unambiguous and named at token granularity, which is what matters in a catalog of hundreds of near-identical per-asset tools. It does not name a sibling or general alternative (e.g. buy_crypto_price or buy_coin_*), so differentiation rests on the token symbol alone.

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 rather than stated: an agent infers 'call this when you need the RAIN price.' There is no when/when-not guidance and no pointer to an alternative for obtaining prices of other assets or for bulk price lookups. The payment and network constraints are given, but the selection logic among siblings is 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