Skip to main content
Glama
bitcompare

Bitcompare MCP Server

Official

Fear & Greed index

fear_greed_index
Read-onlyIdempotent

Retrieve the current Crypto Fear & Greed Index value and analyze historical trends to gauge market sentiment and inform investment decisions.

Instructions

Current Fear & Greed index value and historical trend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesCurrent index, 0 (extreme fear) to 100 (extreme greed)
historyNoRecent trend of the index
updatedAtNo
classificationYesLabel, e.g. `Greed`, `Neutral`, `Extreme Fear`
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds useful context by specifying that the tool returns both the current value and historical trend, which is beyond the annotations.

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?

A single sentence that is concise and front-loaded, containing all necessary information without wasted words.

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

Completeness4/5

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

Given no parameters and the presence of an output schema (not shown), the description adequately summarizes the tool's purpose. However, it could be slightly more complete by mentioning the index range or scale, but the output schema likely covers details.

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?

No parameters exist, so schema coverage is 100%. The baseline for zero parameters is 4, and the description correctly adds no unnecessary parameter details.

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 'current Fear & Greed index value and historical trend,' specifying the verb (provides) and resource (Fear & Greed index). This distinguishes it from sibling tools focused on coin prices, rates, and market summaries.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies its purpose, but does not mention when not to use it or direct users to other tools for related data.

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/bitcompare/mcp-server'

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