Skip to main content
Glama
CohenD

fin-data-mcp-server

by CohenD

Crypto Fear & Greed Index

crypto_fear_greed_index
Read-onlyIdempotent

Access the Crypto Fear & Greed Index to measure market sentiment. Returns current value and configurable history on a scale from 0 (extreme fear) to 100 (extreme greed).

Instructions

Crypto market sentiment index (0 = extreme fear, 100 = extreme greed). Returns the latest value plus history for the requested number of days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of days of history (1 = today only)
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by explaining the output structure (index value plus history) and the meaning of the numeric range. This is consistent with annotations and provides useful context beyond the structured data.

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?

One sentence, front-loaded with key information (market sentiment index and range), no redundancy. Every word earns its place.

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 simple read-only tool with one parameter and no output schema, the description fully explains what the tool returns (latest value plus history) and how the parameter affects output. No gaps remain.

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%, with the 'limit' parameter described as 'Number of days of history (1 = today only)'. The tool description reinforces this but does not add new meaning. Baseline score of 3 is appropriate given high schema coverage.

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 it's a 'Crypto market sentiment index' with explicit range (0-100) and specifies it returns 'the latest value plus history'. This precisely identifies the tool's purpose and distinguishes it from sibling tools like crypto_candles (price data) or crypto_ticker (current ticker).

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 implies usage for market sentiment, but does not explicitly provide when-to-use or when-not-to-use guidance. No alternatives are mentioned, though the unique nature of the tool among siblings reduces the need for exclusion criteria.

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/CohenD/fin-data-mcp'

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