Skip to main content
Glama

Crypto fear greed

crypto_fear_greed
Read-onlyIdempotent

Live Crypto Fear & Greed Index (0-100 score, classification, 1d/7d deltas, 7d/30d averages, trend, and daily history) from Alternative.me. Not financial advice. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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
daysNoOptional number of daily history points (1-30, default 7).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: source attribution, a $0.001 per-call fee, accepted chains/assets, and a required two-step payment negotiation. It stops short of describing what happens on a rejected payment 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.

Conciseness4/5

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

Front-loads what the index returns, then the cost/payment instructions, so the agent gets the value proposition first. The parenthetical payload list is dense but every element names a distinct return field; the payment-chain enumeration is the only slightly verbose part.

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 paid, read-only data tool with no output schema, the description covers returned contents, cost, payment flow, and a disclaimer, which is everything an agent needs to select and invoke it correctly. Remaining gaps (error handling, rate limits) are not essential to choosing or calling the tool.

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 coverage is 100% and already documents the `days` range and default, so the baseline applies. The description does add meaning the schema lacks for `payment` by explaining the no-payment-then-payment call sequence, which is relevant to how the parameter is used.

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 ('Live Crypto Fear & Greed Index') plus the exact returned fields (0-100 score, classification, 1d/7d deltas, 7d/30d averages, trend, daily history) and the data source (Alternative.me). This clearly separates it from siblings like crypto_price or funding_rates.

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 explicit procedural guidance for the payment handshake (call once without `payment` for terms, then again with `payment`), which an agent must follow to succeed. It does not state when to prefer this over sibling sentiment/price tools, but the resource is narrow enough that the omission is minor.

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