Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RECALL

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

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

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 at all, the description carries the full behavioral burden and does well: it discloses pricing ($0.05 USDC on Base), the absence of auth requirements, the billing policy on failures, and the data provenance (Coinbase Exchange with Kraken cross-check). It does not say what the failure modes or latency look like, which keeps it from 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?

Two dense sentences, front-loaded with the cost signal and then the payload contents, with no filler. The raw endpoint URL at the end is arguably dead weight for an agent that only invokes the tool, but it is a minor cost.

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

Completeness5/5

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

There is no output schema, so the description rightly enumerates the returned metrics, and it also covers cost, auth, and failure billing. For a zero-parameter read tool, an agent has everything needed to decide and call correctly.

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 schema semantics to supplement and the baseline is 4-level territory. The description instead spends its words on return fields, which the input schema cannot convey; that is useful but not parameter semantics, so a middle-high score is fair.

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 states a concrete resource and payload: RECALL/USD last price, 24h open/high/low, % change, and 24h/30d volume. It implicitly distinguishes itself from the hundreds of sibling buy_coin_* tools by naming the exact pair (RECALL/USD) and venue sources. However, the tool name's 'buy_' prefix implies a transaction while the description describes a read-only price lookup, creating a mismatch an agent must resolve on its own.

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 context is implied by the price-data payload and the 'No account, no API key' note, and the cost line ('$0.05 USDC on Base', 'Failed calls not charged') helps an agent weigh whether to call. But it never states when to prefer this over alternatives such as buy_crypto_price or the generic buy_coin_* family, nor any when-not condition.

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