Skip to main content
Glama

SouthPow crypto & market data

buy_coin_REQ

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 well: it discloses the cost ($0.002 USDC on Base), that payment happens on-chain, that no authentication is required, that failed calls are not charged, and which exchanges the data comes from. It omits rate limits, data freshness/latency, and the response encoding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the payment flag, then the payload, then cost/auth/billing terms, all in two dense sentences with no filler. Every clause carries actionable information for the caller.

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?

No output schema exists, so the description must describe the return payload, and it does by listing the exact fields returned. Remaining gaps are format (JSON envelope shape) and update cadence, which are minor for a fixed-endpoint price read.

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 the baseline is 4; the description correctly conveys that the ticker is baked into the fixed endpoint URL, leaving nothing for the caller to supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resource (REQ/USD) and enumerates the returned metrics: last price, 24h open/high/low, % change, 24h and 30d volume. Against a sibling set of hundreds of near-identical ticker variants, the ticker in the name plus the explicit REQ/USD scope makes selection unambiguous.

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?

Implies when to call it (you want live REQ/USD price data) and gives practical preconditions (paid, no account or API key). It never names an alternative such as buy_crypto_price or explains when to prefer that broader tool, and gives no guidance on caching or repeated calls despite a per-call cost.

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