Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_fear_greed

Check today’s Crypto Fear & Greed Index (0–100) with its label and attribution to gauge whether the crypto market is fearful or greedy.

Instructions

Use when the user asks how fearful or greedy the crypto market is today. Returns the Crypto Fear & Greed Index (0-100), its label (Extreme Fear to Extreme Greed) and the attribution to show with it; daily. For trend use get_fear_greed_compare. Show attribution with the values. Ex: no parameters Costs $0.005 USDC per call.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return contents (index, label, attribution), the update cadence ('daily'), the zero-parameter nature, and the per-call price of $0.005 USDC. It also imposes an output contract ('Show attribution with the values'). It stops short of error behavior or whether values are cached/stale within the day, keeping it out of the top band.

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-loaded with the trigger and return contents, then the sibling pointer and display instruction. The closing fragment 'Ex: no parameters Costs $0.005 USDC per call' is a run-on with a stray 'Ex:' prefix, which costs a little polish but not comprehension.

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?

There is no output schema, so the description must describe return values and it does (index 0-100, label, attribution). It also covers cost and cadence, which an agent needs before calling a paid endpoint. Only minor gaps remain around response shape and failure modes.

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?

Zero parameters, so the baseline is 4; the description correctly confirms 'no parameters', matching the empty schema. No further parameter meaning is needed or possible.

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 ('Returns the Crypto Fear & Greed Index') with the value range (0-100) and label scale (Extreme Fear to Extreme Greed), and explicitly separates itself from the trend sibling get_fear_greed_compare. An agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ('Use when the user asks how fearful or greedy the crypto market is today') and routes the trend case to get_fear_greed_compare. Both the when-to-use and one when-to-use-something-else condition are stated outright.

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