Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RENDER

Paid. RENDER/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/RENDER.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses pricing, the payment chain/asset, no auth requirement, the failure billing policy, and the upstream data sources (Coinbase Exchange with Kraken cross-check). Gaps remain on caching/freshness, rate limits, and the exact payment handshake, so not 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?

Compact and largely front-loaded: the data payload comes first, then cost and access terms, then the endpoint. The leading "Paid." fragment is slightly clipped, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the field enumeration (price, OHLC, % change, volumes) usefully doubles as a return-value description. However, for a paid tool with zero parameters, the description never explains how the $0.25 USDC payment is actually settled or what a caller receives on payment failure, leaving a real operational gap.

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 ticker, quote currency, and desired metrics are all baked into the description, so no parameter meaning is left ambiguous.

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?

"RENDER/USD live: last price, 24h open/high/low, % change, 24h and 30d volume" states a concrete resource and the exact fields returned, which is enough to tell it apart from the hundreds of ticker-specific siblings. It falls short of 5 because the name says "buy_coin" while the tool only fetches price data, and the description never explicitly addresses that gap.

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?

It gives cost and no-signup context ("$0.25 USDC on Base. No account, no API key. Failed calls not charged"), which implies this is a cheap one-shot lookup. But it never says when to prefer this over buy_crypto_price or the other buy_coin_* siblings, nor any exclusion or prerequisite beyond payment.

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