Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FET

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden well: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, is not charged on failure, and draws from Coinbase Exchange with a Kraken cross-check. Missing only rate limits and latency/refresh expectations, which keeps it below 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.

Conciseness5/5

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

Two tightly packed sentences with the payment caveat front-loaded ('Paid.'), followed by payload contents, pricing/auth terms, and the endpoint URL. No sentence is filler.

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?

With no output schema and no annotations, the description supplies the returned fields, cost, auth model, and failure charging policy, which is enough to call it safely. It stops short of describing response format or freshness guarantees, but nothing essential is missing for invocation.

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 schema baseline is 4 and there is nothing further for the description to disambiguate. The description correctly implies a parameterless, symbol-fixed call.

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 specifies the exact resource and fields returned (FET/USD last price, 24h open/high/low, % change, 24h and 30d volume) with named sources, which clearly overrides the misleading 'buy_coin' name. It is distinguishable from the many sibling buy_coin_<SYMBOL> tools only by the implicit symbol, but that differentiation is inherent to the naming and requires no extra prose.

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 rather than stated: an agent can infer this is the tool for FET spot price data, and the 'Paid' / '$0.10 USDC on Base' lines signal the cost trade-off. However, it never says when to prefer this over the general sibling buy_crypto_price, nor what conditions make the paid call worthwhile.

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