Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FIL

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

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

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 supplied, the description carries the full burden and does a solid job: it discloses the payment model and chain ($0.01 USDC on Base), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, whether the price is spot vs delayed, and the response format, which keeps it short of 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?

Extremely compact and front-loaded with the 'Paid.' signal, then the payload, then cost/auth terms. The telegraphic style is efficient but slightly fragmented, and the trailing raw URL adds little an agent can act on.

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 paid data endpoint with no annotations and no output schema, the description covers what matters: fields returned, data sources, price, payment chain, auth requirements, and failure billing. The main remaining gap is the actual response shape, which no other structured field supplies.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly frames this as a parameterless, fixed-ticker endpoint.

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 exact resource and payload: FIL/USD last price, 24h open/high/low, % change, and 24h/30d volume, plus named sources (Coinbase Exchange, Kraken cross-check). That is far more specific than the bare tool name, which misleadingly reads like a 'buy' action. It never explicitly states it is a read-only price lookup nor distinguishes itself from the ~400 other buy_coin_TICKER siblings beyond the implied ticker.

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 infers it should call this when it needs FIL price data. The pricing context ('$0.01 USDC on Base', 'Failed calls not charged') helps an agent judge whether the call is worth it, but there is no explicit when-to-use/when-not, no mention of the free-looking alternative buy_crypto_price, and no note that this is the FIL-specific variant in a large sibling family.

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