Skip to main content
Glama

Crypto Fear & Greed index

get_fear_and_greed_index
Read-onlyIdempotent

The crypto market's Fear & Greed index (alternative.me), 0 extreme fear to 100 extreme greed, updated once a day: today's value and label, yesterday, a week and a month ago, the 7-day change and the 30-day average. Use to gauge the whole market's mood. Not for one coin's positioning (use get_market_positioning). No inputs. A mood figure, not a signal on its own. Next: get_signal_score.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
as_ofYesThe day the value is for, ISO 8601 UTC
scaleYesWhat the numbers mean
valueYesToday, 0 (extreme fear) - 100 (extreme greed)
sourceYesWhere it comes from
week_agoYesValue 7 days ago, 0-100
month_agoYesValue 30 days ago, 0-100
yesterdayYesYesterday's value, 0-100
average_30dYesMean of the last 30 days, 0-100
deprecationNoPresent only while this tool is deprecated: replacement, removal_date, changelog
classificationYesThe index's own label, e.g. Fear
change_7d_pointsYesToday minus a week ago, index points

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed25 schema fields changed
    • removedInput schema / title
      Removed value: -"get_fear_and_greed_indexArguments"
    • removedOutput schema / properties / as_of / title
      Removed value: -"As Of"
    • removedOutput schema / properties / average_30d / title
      Removed value: -"Average 30D"
    • removedOutput schema / properties / change_7d_points / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / change_7d_points / title
      Removed value: -"Change 7D Points"
    • addedOutput schema / properties / change_7d_points / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedOutput schema / properties / classification / title
      Removed value: -"Classification"
    • addedOutput schema / properties / deprecation / additionalProperties
      Added value: +true
    • removedOutput schema / properties / deprecation / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / deprecation / default
      Removed value: -null
    • removedOutput schema / properties / deprecation / title
      Removed value: -"Deprecation"
    • addedOutput schema / properties / deprecation / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedOutput schema / properties / month_ago / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / month_ago / title
      Removed value: -"Month Ago"
    • addedOutput schema / properties / month_ago / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedOutput schema / properties / scale / title
      Removed value: -"Scale"
    • removedOutput schema / properties / source / title
      Removed value: -"Source"
    • removedOutput schema / properties / value / title
      Removed value: -"Value"
    • removedOutput schema / properties / week_ago / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / week_ago / title
      Removed value: -"Week Ago"
    • addedOutput schema / properties / week_ago / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedOutput schema / properties / yesterday / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / yesterday / title
      Removed value: -"Yesterday"
    • addedOutput schema / properties / yesterday / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedOutput schema / title
      Removed value: -"FearGreed"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, destructive=false, openWorld), so the description's added value is the daily refresh cadence — a real staleness signal an agent needs — plus the third-party source (alternative.me) and the interpretive caveat that it is "a mood figure, not a signal on its own." It does not discuss failure modes if the upstream source is unavailable, 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?

Front-loaded with what the tool returns, then usage, then exclusion, then caveat and next step — a sensible agent-reading order. It is dense and clause-heavy in a single sentence, but nearly every clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-input read tool with an output schema, annotations, and a clearly stated refresh cadence and interpretation caveat, nothing an agent needs in order to call or trust it is missing.

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?

Zero parameters, so the baseline of 4 applies; the description correctly and explicitly confirms "No inputs," removing any doubt about whether date ranges or filters can be passed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (the crypto Fear & Greed index), its source, its 0-100 scale, its daily cadence, and exactly which datapoints come back (today, yesterday, week, month, 7-day change, 30-day average). It is impossible to confuse with any sibling such as get_market_positioning or get_signal_score.

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

Usage Guidelines5/5

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

Explicit when-to-use ("gauge the whole market's mood"), explicit when-not ("Not for one coin's positioning") with the alternative sibling named, plus a forward pointer ("Next: get_signal_score"). This is the full when/when-not/alternative triad.

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