Skip to main content
Glama

feargreed

Get the Crypto Fear & Greed Index to measure market sentiment. Displays fear and greed levels for the past 7 days, helping identify potential market tops and bottoms.

Instructions

Crypto Fear & Greed Index — market sentiment indicator. Shows last 7 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that fetches the Crypto Fear & Greed Index from the alternative.me API. It requests the last 7 days of data and returns value, label (classification), and date for each entry.
    async function getFearGreed() {
      try {
        const data = await fetch('https://api.alternative.me/fng/?limit=7');
        return data.data.map(d => ({
          value: parseInt(d.value),
          label: d.value_classification,
          date: new Date(d.timestamp * 1000).toISOString().split('T')[0],
        }));
      } catch (e) {
        return { error: 'Fear & Greed API unavailable' };
      }
    }
  • Tool definition/schema for 'feargreed' within getToolDefinitions(). The inputSchema is an empty object (no parameters needed), and the description explains it shows the last 7 days of the Crypto Fear & Greed Index.
    {
      name: 'feargreed',
      description: 'Crypto Fear & Greed Index — market sentiment indicator. Shows last 7 days.',
      inputSchema: { type: 'object', properties: {} }
    }
  • index.js:310-316 (registration)
    Registration of the 'feargreed' tool in the getToolDefinitions() array, which is returned when the client calls 'tools/list'.
        {
          name: 'feargreed',
          description: 'Crypto Fear & Greed Index — market sentiment indicator. Shows last 7 days.',
          inputSchema: { type: 'object', properties: {} }
        }
      ];
    }
  • index.js:354-355 (registration)
    The case branch in handleToolCall() that dispatches to getFearGreed() when the tool name is 'feargreed'.
    case 'feargreed':
      return await getFearGreed();
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states it shows last 7 days but omits details like output format, units, or whether any authentication is needed.

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 extremely concise—one sentence that is front-loaded and contains no unnecessary words. Every element is essential for understanding the tool's basic function.

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

Completeness3/5

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

Given no parameters and no output schema, the description is minimally sufficient for a simple information retrieval tool. However, it lacks detail on the exact output shape or value interpretation, which could aid comprehension.

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 has zero parameters, and schema coverage is 100% (vacuously). Per guidelines, 0 parameters yields a baseline score of 4.

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 provides the Crypto Fear & Greed Index, a market sentiment indicator, and specifies it shows the last 7 days. This uniquely identifies its purpose among siblings like 'price' or 'trending'.

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 description does not explicitly guide when to use this tool versus siblings. While the purpose implies sentiment analysis, no contextual usage tips or exclusion criteria are given.

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/ShipItAndPray/mcp-market-data'

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