Skip to main content
Glama

SouthPow crypto & market data

buy_fng_90d

Paid. Crypto Fear & Greed Index, last 90 days with daily values and average. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/fear-greed/90d.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 on commerce: it declares 'Paid', the $0.01 USDC price, accepted chains (Base or Solana), no account/API key needed, and that failed calls are not charged. It still omits anything about the payment handshake, rate limits, latency, or what a success response looks like, so gaps remain for a paid endpoint.

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 with the decisive fact ('Paid') and then tightly layered: what you get, price, payment rails, access model, billing behavior, endpoint URL. Fragments rather than sentences, but nothing is redundant.

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, and the description compensates by stating the payload contents (daily values plus an average). Combined with cost and payment rails, an agent has enough to decide and invoke; only return format details and the exact payment protocol are left unstated.

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. It correctly avoids inventing inputs and the empty schema matches the no-argument invocation.

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?

States a specific verb+resource (buy the Crypto Fear & Greed Index) and pins the scope to 'last 90 days with daily values and average'. That range distinguishes it from buy_fng_7d, buy_fng_30d and buy_fng_now without naming them, but the sibling differentiation is only implicit.

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?

The 90-day window implies when this is the right pick over the 7d/30d/now variants, but the description never says so explicitly and offers no exclusion or alternative guidance. Usage must be inferred from the tool name and range.

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