Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_fear_greed_history

Retrieve daily Fear & Greed Index values and classifications for a chosen date range or last N days to chart, backtest, or compare against price; raw series includes attribution.

Instructions

Use when the user wants the Fear & Greed time series to chart, backtest or compare with price. Returns daily value and classification for the last days (max 365) or start_date to end_date (YYYY-MM-DD), with attribution. Raw series, no summary. Show attribution with the values. Ex: days=90 Costs $0.005 USDC per call.

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": "get_fear_greed_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses return contents (daily value plus classification), a hard cap (max 365), accepted date formats, a display obligation for attribution, and a per-call cost of $0.005 USDC. The gaps are conflict/precedence behavior when both `days` and a date range are supplied, and what an invalid or out-of-range request yields.

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?

Front-loaded with the usage trigger, then returns, then constraints, then cost, with no padding sentences. The telegraphic fragments ('Raw series, no summary', 'Ex: days=90') are efficient but slightly clipped, and the cost sentence sits awkwardly appended to the example.

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 3-parameter, no-output-schema tool, the description usefully covers return shape, limits, date formats, attribution handling, and pricing. What is missing is the interaction rule between the two input modes, which matters because both are optional in the schema.

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 description coverage is 0%, so the description must compensate, and it does: it bounds `days` (max 365), gives the YYYY-MM-DD format for start_date/end_date, and supplies a worked example (days=90). It does not state which takes precedence if both `days` and a start/end range are passed, nor that omitting everything defaults to 30.

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?

States a specific verb and resource ('Fear & Greed time series') and explicitly scopes it as 'Raw series, no summary', which separates it from a summary/current-value sibling such as get_fear_greed. The stated use cases (chart, backtest, compare with price) make the resource concrete.

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?

Gives clear when-to-use framing ('Use when the user wants the Fear & Greed time series to chart, backtest or compare with price'), which is more than most definitions offer. It stops short of naming an alternative tool or stating when NOT to use it (e.g., for a single current reading, use the point-in-time sibling).

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