Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

get_crypto_fear_greed_index

Read-onlyIdempotent

utilpeek: Get the crypto Fear & Greed Index: market sentiment value, label and 7-day history. For local exchange premiums use get_local_crypto_premiums. Returns the crypto Fear & Greed Index (alternative.me): value 0-100, label and the last 7 daily values, with source and attribution in the reply. One value per day from an hourly cache; the attribution to alternative.me must stay next to the data. No cache, or older than 3 days, is a 503 (not charged). Informational only, not investment advice. Typically under 0.1 s (served from the cache). Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/crypto-fear-greed-index-api.html

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_crypto_fear_greed_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
as_ofNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
labelNo
scaleNo
staleNo
valueNo
sourceNo
disclaimerNo
history_7dNo
attributionNo
retrieved_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / title
      Removed value: -"get_crypto_fear_greed_indexArguments"
    • removedOutput schema / properties / attribution / description
      Removed value: -"credit to alternative.me; carry it next to the data"
    • removedOutput schema / properties / history_7d / description
      Removed value: -"newest first, one value per UTC day"
    • removedOutput schema / properties / history_7d / items
      Removed value: -{
      -  "properties": {
      -    "date": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "label": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "value": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "name": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "notice": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "terms": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / value / description
      Removed value: -"0 = extreme fear, 100 = extreme greed"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/open-world; the description adds genuinely new behavior: hourly cache with one value per day, a 503 when the cache is missing or older than 3 days (and that such calls are not charged), sub-100 ms latency, the USD 0.001 price, a 10-calls-per-IP-per-day free tier, and a mandatory alternative.me attribution requirement.

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?

Purpose is front-loaded in the first clause, and the pricing, quota, cache-failure, and documentation details all bear on whether an agent should call it. It is a dense semicolon chain rather than a structured block, which slightly hurts scanability but nothing is redundant filler.

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?

With zero parameters, an output schema, and full annotation coverage, the description closes the remaining gaps an agent would care about: source, granularity, failure mode, cost, and quota. Nothing needed to call it correctly 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, which is the baseline-4 case; there is nothing for the description to disambiguate, and the schema is fully self-describing for an empty object.

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 ('Get the crypto Fear & Greed Index') plus exactly what comes back (value 0-100, label, 7-day history) and the upstream source (alternative.me), so it is distinguishable from siblings like get_local_crypto_premiums.

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 routes one adjacent use case elsewhere ('For local exchange premiums use get_local_crypto_premiums'), and the note 'One value per day from an hourly cache' signals the daily granularity that rules out intraday use. It stops short of a full when-not list, but the selection guidance is clear.

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.