Skip to main content
Glama
Sign In
Universal Crypto MCP

Universal Crypto MCP

by nirholas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

market_analyze_fear_greed_trend

Analyze Fear & Greed Index trends over 2-365 days to calculate average sentiment and determine market trend direction.

Instructions

Analyze trends in the Fear & Greed Index over a specified period, calculating averages and trend direction

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": "<days>"
    },
    "name": "market_analyze_fear_greed_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesNumber of days to analyze (2-365)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (calculating averages and trend direction) but does not mention any limitations, edge cases, or what the output structure looks like. It is not misleading, but lacks additional behavioral context.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's purpose and outputs with no filler or redundancy.

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?

The tool is simple with one well-documented parameter. The description explains the main outputs (averages and trend direction) and the context of analyzing a specified period. While there is no output schema, the description provides sufficient clarity for this low-complexity 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 description coverage is 100% with a clear description for 'days' (2-365). The tool description adds the phrase 'over a specified period' which aligns with the parameter but provides no additional semantic detail beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool's function: analyzing trends in the Fear & Greed Index over a period, with specific outputs (averages, trend direction). This distinguishes it from siblings like market_get_fear_greed_current and market_get_fear_greed_historical, which simply fetch current or historical values.

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 usage for trend analysis over a specified period but does not explicitly state when to use this tool versus alternatives like market_get_fear_greed_historical. There are no exclusions or alternative recommendations, so guidance is only implied.

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

Deploy Server

Other Tools