Skip to main content
Glama
ymylive
by ymylive

get_fear_greed_index

Retrieve the Crypto Fear & Greed Index to measure market sentiment on a scale from 0 (extreme fear) to 100 (extreme greed). Useful as a contrarian indicator for timing trades based on crowd emotion.

Instructions

Get the Crypto Fear & Greed Index (0=extreme fear, 100=extreme greed).

A widely-quoted contrarian sentiment indicator that combines volatility, momentum, social media, surveys, BTC dominance and trend volume into a single 0-100 score. Useful for "are people fearful or greedy right now?" questions.

Args: limit: How many days of history to return (default 1 = today only, 0 = all history).

Returns: Object with name, data (array of { value, value_classification, timestamp, time_until_update }), and metadata. Higher = greedier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
Behavior4/5

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

The description explains the index as a contrarian indicator, details the components (volatility, momentum, etc.), and specifies that higher values mean greedier. With no annotations, it provides sufficient behavioral context.

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?

The description is structured with a clear purpose statement, context, and Args/Returns sections. It is efficient but slightly longer than necessary; still, every sentence adds value.

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?

Given the simplicity (one parameter, no output schema), the description fully covers usage, parameter semantics, and return format, including field details and interpretation. No gaps.

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

Parameters5/5

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

Despite 0% schema description coverage, the description's Args section thoroughly explains the 'limit' parameter, including defaults and special value (0 = all history), adding meaning beyond the schema's type and default.

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?

The description clearly states the tool retrieves the Crypto Fear & Greed Index, defines the 0-100 scale, and distinguishes it from sibling tools by focusing on a specific sentiment indicator.

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

Usage Guidelines4/5

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

The description suggests use for 'are people fearful or greedy right now?' questions, indicating appropriate context. It does not explicitly exclude cases or mention alternatives, but the guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ymylive/coin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server