Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

fear-greed

[x402 paid: $0.002 USDC on Base] Crypto Fear & Greed Index with 10-day history — market sentiment for timing decisions. tools/call returns the live payment challenge.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, this description does unusually useful work: it discloses the x402 paid model, the exact price ($0.002 USDC on Base), and that tools/call returns a live payment challenge rather than data. That last detail is the key non-obvious behavior for an agent. It stops short of describing rate limits or what a successful paid response looks like beyond the 10-day history.

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 tight sentences: the price and payment caveat are placed first, then the value proposition. No filler, no repetition of the tool name, and the most operationally important fact (payment challenge) is not buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description covers what matters: what the index is, that history spans 10 days, and that calls incur an x402 payment step. Missing only the shape of a successful response (e.g., numeric value and classification), which is a modest gap for this complexity.

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. The empty schema is consistent with the description's framing of a single fixed lookup.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Crypto Fear & Greed Index) and its payload (10-day history) plus the intended use (market sentiment for timing decisions). It is clear what the tool returns, though it does not explicitly distinguish itself from sentiment-adjacent siblings such as market-pulse.

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?

Usage is implied by the phrase 'market sentiment for timing decisions', which suggests a trading/timing context. There is no explicit when-to-use vs when-not guidance and no named alternative for broader market data, so the agent must infer fit from sibling names alone.

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