boo-x402-mcp

by lucle87

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Crypto Fear & Greed index

fear_greed

Get the current Crypto Fear & Greed index and label to gauge overall market sentiment. No input required; pay per call.

Instructions

Current Crypto Fear & Greed index (0-100) and its label. Use to gauge overall market sentiment. No input.

PAID TOOL: up to $0.005 USDC per call (x402 on Base). Paid automatically from your configured wallet.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations provided, but description discloses that it is a read-only tool with no input, and importantly mentions it is a paid tool with cost details (up to $0.005 USDC per call). This adds behavioral context beyond just stating it's a read operation.

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 plus pricing information, all front-loaded. Every sentence provides essential information with zero waste.

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?

Given zero parameters, no output schema, and no annotations, the description fully informs the agent: what it returns (index and label), how to use it (gauge sentiment), and cost. No gaps.

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?

No parameters exist, and schema coverage is 100%. Description adds value by confirming 'No input', which helps the agent understand that no parameters are needed. Baseline for zero params is 4.

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?

Description clearly states it returns the Crypto Fear & Greed index (0-100) and its label, with a clear purpose to gauge market sentiment. It distinguishes itself from sibling tools, as no other sentiment index tool is present.

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 says 'Use to gauge overall market sentiment', providing clear context. No exclusions or alternatives mentioned, but sibling tools are diverse and none directly compete, so minimal guidance needed.

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