Skip to main content
Glama

SouthPow crypto & market data

buy_coin_REZ

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

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

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 zero annotations, the description carries the full burden and does disclose the traits that matter most for a paid endpoint: it is a paid call, the price is $0.01 USDC on Base, no account or API key is needed, failed calls are not charged, and the data provenance is stated. It omits rate limits, response encoding, and whether the snapshot is cached, 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?

It is short and front-loaded with the most decision-relevant token ('Paid.'), then the payload, then cost/auth, then URL. The telegraphic field-list style ('24h open/high/low') is efficient, though the fragmentary grammar makes a couple of clauses slightly harder to parse than a plain sentence.

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 tool, the description covers the returned fields, the data sources, the payment model, the auth requirement, the billing behavior on failure, and the endpoint URL — enough for an agent to call it correctly. Missing only response format and freshness/latency guarantees.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste space on input arguments.

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 concrete resource and payload: 'REZ/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus the upstream sources (Coinbase Exchange, Kraken cross-check). That is far more specific than the tool name, which misleadingly says 'buy_coin' for what is actually a price-data lookup. It does not differentiate itself from the generic buy_crypto_price sibling, so it stops short of a 5.

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 context of use ('Paid... $0.01 USDC on Base. No account, no API key. Failed calls not charged') which tells an agent the cost and auth model, but never says when to pick this per-asset endpoint versus the generic buy_crypto_price or any other sibling. There are no explicit exclusions, so usage must be inferred from the ticker in the name.

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