Skip to main content
Glama

crypto_fear_greed

Crypto Fear and Greed Index for market-sentiment checks: the latest 0-100 value and classification (Extreme Fear to Extreme Greed), plus optional recent daily history. Optional limit (1-31, default 1). Data from alternative.me. Commercial use of this index is allowed with attribution, which is included in every response. Pay per call in USDC on Base. Price $0.002 USDC per call via x402. Example output: {"source":"alternative.me Crypto Fear and Greed Index","source_url":"https://alternative.me/crypto/fear-and-greed-index/","attribution":"Crypto Fear and Greed Index data from alternative.me.","latest":{"value":10,"classification":"Extreme Fear","at":"2026-11-16T00:00:00.000Z","timestamp":"1794787200

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Number of recent daily values to return, 1 to 31, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/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, and it does substantial work: it discloses the upstream source (alternative.me), the attribution/licensing terms, and — critically — that each call is a paid x402 transaction costing $0.002 USDC on Base. That payment requirement is exactly the kind of behavior an agent must know before invoking. It falls short of 5 because the example output is cut off mid-JSON and nothing is said about error behavior or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the limit semantics are front-loaded, which is good, but the pricing is stated twice ("Pay per call in USDC on Base" then "Price $0.002 USDC per call via x402") and the example output is truncated mid-object, leaving a dangling, unhelpful fragment that weakens an otherwise tight description.

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 single-optional-parameter read tool with no output schema, the description covers what an agent needs: what is returned (latest value, classification, timestamp, optional history), where it comes from, attribution obligations, and the payment model. The incomplete example output and absent error/pagination notes are the only gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the single `limit` parameter is already fully documented as 1-31 with default 1. The description restates the same range and default without adding format or behavior detail (e.g., ordering of returned history). Baseline 3 is appropriate when the schema does the work.

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: the Crypto Fear and Greed Index, the latest 0-100 value with classification (Extreme Fear to Extreme Greed), plus optional recent daily history. An agent can immediately tell this is a market-sentiment read. It does not explicitly distinguish itself from a sibling like macro_indicators, so it stops short of 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?

"For market-sentiment checks" implies the usage context but gives no explicit when-to-use/when-not rules and names no alternative tool. With a sibling such as macro_indicators present, a sentence clarifying that this index is crypto-specific sentiment rather than general macro data would have earned a higher score.

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