Crypto Bot Audit + Market Data (x402 paid)

Crypto fear and greed index

market_fear_greed_index

Read-onlyIdempotent

The alternative.me fear-and-greed reading: index value, its label and the seconds until the next update, for today or a whole history back to 365 days. Costs $0.001 USDC per call. Byte-identical to GET /market/fear-greed-index?limit=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	daily readings to return, newest first (max 365) (default 1)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`name`	No
`note`	No
`rows`	No
`count`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`latestValue`	No
`timeUntilUpdateSec`	No
`latestClassification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "latestClassification": {
+      "type": "string"
+    },
+    "latestValue": {
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "timeUntilUpdateSec": {
+      "type": "integer"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint). The description adds genuine context beyond annotations: the cost per call, the returned fields, the historical range, and byte-identical behavior to a REST endpoint. No contradiction exists.

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 no filler. The core behavior is front-loaded, followed by cost and endpoint equivalence. Every clause earns its place.

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 an output schema present and only one optional parameter, the description is complete: it covers scope, cost, response contents, and endpoint equivalence. 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.

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents the single 'limit' parameter. The description does not add parameter-level semantics beyond the schema, which fits the baseline of 3 for high coverage.

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 returns the alternative.me fear-and-greed reading, including index value, label, and seconds until next update. It also clarifies the temporal scope (today or history back to 365 days), which differentiates it from the many exchange-data siblings in the market_* group.

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?

The description implies when to use the tool (when a fear-and-greed index reading is needed) and notes the $0.001 USDC cost, but it does not name alternative tools or state explicit exclusions. Since no sibling covers the same data source, the omission is minor, but the guidance is implied rather than explicit.

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

All Crypto Bot Audit + Market Data (x402 paid) 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.

Resources

Need Help?