Skip to main content
Glama
Sign In
tokenguard-mcp

tokenguard-mcp

by eltociear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_fear_greed

Get current and historical Crypto Fear & Greed Index values to measure market sentiment from extreme fear to extreme greed.

Instructions

Get the Crypto Fear & Greed Index (0=Extreme Fear, 100=Extreme Greed)

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of historical days to return (default: 7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so description must cover behavioral aspects. It states the index range but does not disclose whether the operation is read-only, rate limits, data freshness, or any side effects. For a simple read tool, this is minimally adequate.

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?

Single sentence with no wasted words. All important information is front-loaded: action, resource, and value interpretation.

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 simple index with one optional parameter and no output schema, the description is nearly complete. It explains the meaning of the values, though it could be improved by noting that historical data is returned as an array.

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 already documents the single parameter 'limit' with description and default. The tool description adds no additional meaning beyond schema coverage of 100%.

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 identifies the tool as retrieving the Crypto Fear & Greed Index with its numeric range interpretation. Distinguishes from sibling tools that provide different crypto data (price, gas fees, TVL, etc.).

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?

No explicit guidance on when to use this tool versus alternatives. The sibling list implies it's for market sentiment, but no direct comparison or context is provided.

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