Skip to main content
Glama

Fear & Greed index

fear_greed_index
Read-only

Crypto Fear & Greed composite index. Aggregates Alternative.me index with CoinGecko market signals (market cap change, volume ratio, BTC dominance). Returns 0-100 score, classification (Extreme Fear to Extreme Greed), 7-day trend, historical comparison, and actionable signal summary. Costs $0.002 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
includeHistoryNoInclude 30-day daily history (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond that: the index is composite, the external data sources are named, and the $0.002 USDC per-call cost is disclosed.

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?

The description is dense and front-loaded: it states the index, sources, return contents, and cost in three efficient sentences with no filler. Every sentence adds relevant 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?

Although there is no output schema, the description sufficiently lists what is returned: a 0-100 score, classification, 7-day trend, historical comparison, and signal summary. Combined with the fully described single parameter and annotations, an agent has enough context to call the tool correctly.

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 description coverage is 100%, so the single includeHistory parameter is already documented in the schema. The description mentions historical comparison and 7-day trend but does not explicitly explain the includeHistory flag, so it adds little parameter-level meaning beyond the schema.

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 clearly identifies a specific resource: a Crypto Fear & Greed composite index built from Alternative.me and CoinGecko signals. It is much more specific than a generic sentiment tool, though it does not explicitly distinguish itself from the sibling crypto_sentiment tool.

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 implied by the name and the listed outputs, suggesting it is for gauging crypto market sentiment. However, there is no explicit guidance on when to use this instead of siblings such as crypto_sentiment, nor any when-not-to-use conditions.

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