Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FAI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 burden and does well: it discloses that the call is paid ($0.002 USDC on Base), requires no account or API key, that failed calls are not charged, and which exchanges feed the data. It omits rate limits and the response encoding, so it stops short of complete.

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?

The 'Paid.' lead is well front-loaded and the sentences are dense with useful facts. The trailing raw URL is somewhat redundant for an MCP caller and the bullet-less telegraphic style takes a moment to parse, but there is little wasted text.

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, no-annotation tool, the description supplies cost, billing behavior, data provenance, and returned fields. It could say more about the response shape (JSON structure, units, timestamps) and staleness/latency, which matters for a live 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; the description correctly implies there is nothing to supply and bakes the symbol into the endpoint. No parameter meaning is added or needed.

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 specific resource (FAI/USD live price) and enumerates exactly which fields come back (last, 24h open/high/low, % change, 24h and 30d volume), which is far more informative than the opaque 'buy_coin_FAI' name. It does not explicitly reconcile the name ('buy') with the actual read-only price lookup, so an agent scanning sibling names still has to read the description to know this is data retrieval, not a trade.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus buy_crypto_price or the hundreds of other buy_coin_* siblings. The content implies a price-fetch use case, but the agent is left to infer selection criteria and any exclusions.

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