Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RED

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

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

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 present, the description carries the full burden and mostly does: it discloses the paid nature, the exact price ($0.10 USDC on Base), the payment rail, that no account or API key is required, and that failures are not charged. It also names the upstream data sources (Coinbase Exchange, Kraken cross-check) and the endpoint URL. The only gap is rate limiting and what a successful vs. failed response looks like.

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?

Telegraphic and front-loaded: payment status leads, then data content, then price and prerequisites, then the URL. Nearly every clause carries information. The fragment style is terse but not wasteful; the explicit URL at the end is a minor stylistic cost but useful for 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?

There is no output schema, but the description compensates by enumerating the returned fields (OHLC, % change, 24h/30d volume) and the sources they come from. Combined with the payment and auth terms, an agent has enough to decide to call it and to interpret the result. Only pagination/failure-mode detail is missing, which is minor for a single-object price feed.

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 there is nothing further to disambiguate. The description correctly implies no inputs are needed ('No account, no API key'), consistent with the empty schema.

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 exact resource (RED/USD) and enumerates the returned metrics: last price, 24h open/high/low, % change, 24h and 30d volume. It is specific enough that an agent knows this is a market-data retrieval for a single ticker, clearly distinct from the many sibling buy_coin_* tickers. It does not explicitly contrast itself with buy_crypto_price, leaving that inference to the agent.

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?

The leading 'Paid.' plus the '$0.10 USDC on Base' and 'Failed calls not charged' lines give the agent a real cost-based decision signal, which is better than nothing. However, there is no explicit statement of when to prefer this over a free sibling like buy_crypto_price or over searching for prices another way. Usage is implied rather than prescribed.

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