Skip to main content
Glama

Crypto Fear & Greed Index

fear_greed_index
Read-only

Today's 0-100 crypto Fear & Greed reading built from futures data, with its four component scores.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fear_greed_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds genuine context beyond that: the value scale (0-100), the underlying data source (futures data), and the fact that four component scores accompany the headline reading. It does not cover freshness lag or rate limits, but for a read-only zero-parameter tool the disclosure is solid.

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?

A single well-formed sentence with no filler, and the payload (today's 0-100 reading) is front-loaded. The trailing clause about component scores is informative rather than redundant.

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?

For a parameterless read-only tool with no output schema, an agent mainly needs to know what it returns and when it is current. The description supplies the scale, the data source, and the shape of the response (headline plus four components). It could name the four components or note refresh cadence, but nothing essential to correct invocation is missing.

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 takes zero parameters, so the schema has nothing to explain and the baseline is 4. The description correctly implies no input is needed by framing the tool purely as a reading of today's value.

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 names a specific resource and scope: 'Today's 0-100 crypto Fear & Greed reading built from futures data, with its four component scores.' That tells an agent exactly what data comes back and how it is composed, which meaningfully separates it from the sibling altcoin_season_index. It stops short of explicitly naming that sibling, so it is not a 5.

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 word 'Today's' implies this is a current-snapshot tool rather than a historical query, which is a useful usage boundary. However, there is no explicit guidance on when to call this versus related sentiment or market-overview tools, and no stated prerequisites. Usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources