crypto-feargreed-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_fng_toolB | Get the current Crypto Fear & Greed Index as a tool. |
| get_historical_fng_toolC | Get historical Fear & Greed Index for specified number of days as a tool. Parameters: days (int): Number of days to retrieve (must be a positive integer). Returns: str: Historical Fear & Greed Index values for the specified period. |
| analyze_fng_trendA | Analyze trends in Crypto Fear & Greed Index over specified days. Parameters: days (int): Number of days to analyze (must be a positive integer). Returns: str: A string containing the analysis results, including latest value, average value, trend direction, and number of data points analyzed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| interpret_fng | Generate an interpretation of a Fear & Greed Index value |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| fng://current |
TDQS
Scored across 3 tools
The tools have overlapping purposes that could cause confusion. 'analyze_fng_trend' and 'get_historical_fng_tool' both retrieve historical data with a 'days' parameter, making their boundaries unclear. 'get_current_fng_tool' is distinct but the other two appear to serve similar functions with minor differences in output format.
The naming follows a mixed convention. 'analyze_fng_trend' uses snake_case with a verb_noun pattern, while 'get_current_fng_tool' and 'get_historical_fng_tool' also use snake_case but append '_tool' inconsistently. The pattern is readable but lacks full consistency across all tools.
With 3 tools, the count is reasonable for a focused server on Crypto Fear & Greed Index data. It's slightly thin but covers current, historical, and trend analysis, which aligns well with the domain scope without being overly complex.
The tool surface covers basic retrieval and analysis of the index, but there are notable gaps. For example, there's no tool for comparing multiple time periods, setting alerts, or integrating with other crypto data, which could limit agent workflows in a broader crypto analysis context.