Skip to main content
Glama
kukapay

crypto-feargreed-mcp

get_current_fng_tool

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

Instructions

Get the current Crypto Fear & Greed Index as a tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:62-66 (handler)
    The handler function for the 'get_current_fng_tool' tool. It is decorated with @mcp.tool() for registration and delegates to the helper get_current_fng() after logging.
    @mcp.tool()
    async def get_current_fng_tool(ctx: Context) -> str:
        """Get the current Crypto Fear & Greed Index as a tool."""
        ctx.info("Fetching current Fear & Greed Index")
        return await get_current_fng()
  • main.py:14-32 (helper)
    Supporting resource function that implements the core logic of fetching and formatting the current Crypto Fear & Greed Index from the API endpoint.
    @mcp.resource("fng://current")
    async def get_current_fng() -> str:
        """Get the current Crypto Fear & Greed Index"""
        try:
            async with httpx.AsyncClient() as client:
                response = await client.get(API_URL, params={"limit": 1})
                response.raise_for_status()
                data = response.json()["data"][0]
                timestamp = datetime.fromtimestamp(int(data["timestamp"]))
                return (
                    f"Crypto Fear & Greed Index (as of {timestamp} UTC):\n"
                    f"Value: {data['value']}\n"
                    f"Classification: {data['value_classification']}"
                )
        except httpx.HTTPStatusError as e:
            return f"Error fetching current FNG: {str(e)}"
        except Exception as e:
            return f"Unexpected error: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does without mentioning any behavioral traits such as rate limits, authentication needs, data freshness, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 concise and front-loaded in a single sentence: 'Get the current Crypto Fear & Greed Index as a tool.' It efficiently conveys the core purpose without unnecessary details. However, the phrase 'as a tool' is redundant and could be omitted for better clarity.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks context on usage guidelines, behavioral traits, or output format. For a tool with no structured data to rely on, the description should provide more completeness to aid the agent effectively.

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 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the absence of parameters. A baseline score of 4 is appropriate as the description doesn't need to compensate for any parameter gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get the current Crypto Fear & Greed Index'. It specifies the verb 'Get' and the resource 'Crypto Fear & Greed Index', making the function unambiguous. However, it doesn't explicitly differentiate from its sibling tools (analyze_fng_trend, get_historical_fng_tool), which would require mentioning it retrieves only the current value versus historical data or trend analysis.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tools (analyze_fng_trend, get_historical_fng_tool) or specify contexts like needing real-time data versus historical analysis. Without such distinctions, the agent lacks clear usage instructions.

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/kukapay/crypto-feargreed-mcp'

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