Skip to main content
Glama
Sign In
The Stall

The Stall

by thebrierfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

market-sentiment

Combine Fear & Greed Index and BTC/ETH implied volatility to identify market regimes. Use to calibrate DeFi positions, yield farming risk, or agent spending in volatile conditions.

Instructions

Combined crypto market sentiment signal: Crypto Fear & Greed Index (alternative.me, 0–100, 30-day trend) plus BTC and ETH Implied Volatility from Deribit options market (annualized %). Free upstream sources, no keys. Returns current FGI value, classification (Extreme Fear to Extreme Greed), 7-day FGI trend, IV trend (RISING/FALLING/FLAT), and a composite regime label (CAPITULATION_ZONE, OVERHEATED, COMPLACENT_GREED, CALM_MARKET, etc.). Use before making large DeFi positions, calibrating yield farming risk, or routing agent spend in volatile conditions.

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": "market-sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
history_daysNoNumber of past daily FGI readings to include in response (1–30). Default 7.
include_ivNoWhether to fetch Deribit BTC/ETH implied volatility (adds ~500ms). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Fully transparent: discloses upstream sources (alternative.me, Deribit), free access, no keys, returns detailed outputs including classification, trends, and composite regime. Also notes latency impact of 'include_iv' parameter.

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?

Concise yet comprehensive: front-loaded with main function, no filler sentences. Every sentence adds value.

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?

No output schema, but description thoroughly explains all return values (FGI value, classification, trends, composite regime). Covers inputs, outputs, and use cases completely.

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?

Schema covers 100% of parameters. Description adds useful context: default value for 'history_days' (7) and latency cost for 'include_iv' (~500ms).

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 provides a combined crypto market sentiment signal, explicitly mentioning the Fear & Greed Index (FGI) and implied volatility (IV), and distinguishes itself from sibling tools like 'crypto-fear-greed' by being a composite signal with a regime label.

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

Usage Guidelines4/5

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

Explicitly tells when to use: 'before making large DeFi positions, calibrating yield farming risk, or routing agent spend in volatile conditions.' Does not mention alternatives or when not to use, but provides clear context.

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

Deploy Server

Other Tools