Skip to main content
Glama

The Crypto Fear & Greed Index today and for the previous

crypto_fear_greed
Read-only

The Crypto Fear & Greed Index today and for the previous days (up to 30), with its classification (extreme fear to extreme greed). Attribution: alternative.me. Information only, not financial advice. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "crypto_fear_greed"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo1 to 30 days (default 1)

Output Schema

NameRequiredDescriptionDefault
todayNo
sourceNo
historyNo
checkedAtNo
disclaimerNo
attributionNo

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?

Annotations already declare readOnlyHint and openWorldHint, and the description adds material context beyond them: per-call cost of $0.002, payment rail (x402, USDC on Base/Solana and others), and that failed calls are not charged. That billing detail is genuinely decision-relevant for an agent and is not in the annotations. Return format and rate limiting are left to the output schema.

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 sentences, front-loaded with what the index is and the lookback window, followed by a compact attribution/pricing/disclaimer block. No filler and nothing buried.

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 one-optional-parameter read tool with an output schema and read-only annotations, the description covers scope, classification range, attribution, and cost model. Only explicit usage guidance against sibling indicator tools is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'days' parameter is already documented as '1 to 30 days (default 1)'. The description's 'up to 30' merely restates the schema bound, adding no new syntax or edge-case meaning, so baseline 3 applies.

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?

Names the specific resource (Crypto Fear & Greed Index) and the scope (today plus up to 30 previous days) with the classification range. It is clear what the tool returns, though it never distinguishes itself from a potentially overlapping sibling like crypto_indicators.

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 by the subject matter; there is no explicit statement of when to reach for this versus another indicator tool, nor any exclusions. The 'information only, not financial advice' line is a disclaimer rather than selection guidance.

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