Agent Einstein — Crypto & Market Intelligence

Crypto & TradFi Fear and Greed

get_market_sentiment

Read-onlyIdempotent

Multi-source market sentiment in one read: the crypto Fear & Greed index, CoinMarketCap’s variant, the traditional-market (CNN) Fear & Greed, and the Altcoin Season index. Useful for framing any "how is the market feeling" question.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`cmc`	No	CoinMarketCap Fear & Greed index, with a yearly high/low.
`crypto`	No	Crypto Fear & Greed index, with yesterday/last-week comparisons.
`reason`	No	Why the payload is absent, when `available` is false.
`tradfi`	No	CNN TradFi Fear & Greed index — the equities read, for divergence.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.
`fetchedAt`	No	Per-source refresh times; the four sources age independently.
`altcoinSeason`	No	Altcoin-season regime, its 30d/90d indices and the cohort behind them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "altcoinSeason": {
+      "additionalProperties": true,
+      "description": "Altcoin-season regime, its 30d/90d indices and the cohort behind them."
+    },
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "cmc": {
+      "additionalProperties": true,
+      "description": "CoinMarketCap Fear & Greed index, with a yearly high/low."
+    },
+    "crypto": {
+      "additionalProperties": true,
+      "description": "Crypto Fear & Greed index, with yesterday/last-week comparisons."
+    },
+    "fetchedAt": {
+      "additionalProperties": true,
+      "description": "Per-source refresh times; the four sources age independently."
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "tradfi": {
+      "additionalProperties": true,
+      "description": "CNN TradFi Fear & Greed index — the equities read, for divergence."
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context about the aggregated nature of the data ('in one read' and the source list), but doesn't go into deeper behavioral details like staleness or update frequency. That's acceptable given the annotations carry the safety profile.

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?

Two sentences with zero waste: the first names exactly what the tool returns, the second states its purpose. Front-loaded and scannable.

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?

For a no-parameter read with an existing output schema and safety annotations, the description is complete. It lists every data source and provides a crisp use case; nothing an agent needs to invoke 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 has zero parameters, so the schema trivially covers 100% of parameter semantics. Per the baseline for zero-parameter tools, a 4 is appropriate; no description-level parameter documentation is needed.

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 states a specific verb and resource: it reads multi-source market sentiment, and lists exactly four indices (crypto Fear & Greed, CoinMarketCap’s variant, CNN Fear & Greed, Altcoin Season index). This level of specificity clearly distinguishes it from sentiment-adjacent siblings like get_social_hype or scan_market.

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?

The description explicitly states when to use the tool: 'Useful for framing any “how is the market feeling” question.' However, it does not name alternatives or state when not to use it, which keeps it just below a 5.

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

All Agent Einstein — Crypto & Market Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.