Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FORTH

Paid. FORTH/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/FORTH.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 load and does so well: it discloses that the call is paid, the exact price and payment chain, that no credentials are needed, that failures are not billed, and that data comes from Coinbase Exchange with a Kraken cross-check. Missing only things like latency, caching, or rate limits.

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?

Front-loaded and extremely dense — cost and the returned fields come first, mechanics and the endpoint URL last. The telegraphic style ('24h open/high/low') is efficient, though the raw URL is more of a debugging artifact than decision-relevant information.

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 this is close to sufficient: the description itself lists the returned fields and the payment terms. The remaining gap is that it never clarifies the buy_coin_* naming versus the fact that this returns price data rather than executing a purchase.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly presents the tool as taking no input and fixes the asset and quote currency instead of leaving them as implicit arguments.

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 a concrete verb-resource pair — live FORTH/USD price — and enumerates the exact fields returned (last price, 24h open/high/low, % change, 24h and 30d volume). Against hundreds of near-identical buy_coin_* siblings, the description confirms the asset and the data shape, which the name alone only implies.

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 is only implied: an agent needing live FORTH/USD spot data. It gives strong economic context ($0.10 USDC on Base, no account or API key, failed calls not charged) but never names alternatives such as buy_crypto_price or explains when-not to call this, which matters in a catalog of parallel per-asset price tools.

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