Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_fear_greed_compare

Compare current crypto Fear & Greed with yesterday, 7-day, and 30-day values to determine whether market sentiment is improving or worsening, including changes and attribution.

Instructions

Use when the user asks whether crypto sentiment is improving or worsening. Returns Fear & Greed now with its label, the values yesterday, 7 and 30 days ago, the changes (change_1d, change_7d, change_30d) and the attribution. Show attribution with the values. Ex: no parameters Costs $0.002 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_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 disclosure burden. It reveals the return structure, notes that attribution should be shown, and states the cost of $0.002 USDC per call. It does not discuss error behavior or rate limits, but for a zero-parameter read tool the key behavioral facts are present.

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?

The description is short and front-loads the usage condition before describing the return values. The final sentence is awkwardly concatenated ('Ex: no parameters Costs $0.002 USDC per call.'), but the overall content is efficient and free of extraneous explanation.

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 and no output schema, the description adequately explains what the tool returns and when to use it. It also includes the per-call cost, which is important operational context not available from structured fields.

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 has zero parameters, so there is no parameter semantics burden. The description notes 'no parameters,' which is consistent with the empty input schema and helps confirm there is no additional filtering input.

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 states a specific purpose: answering whether crypto sentiment is improving or worsening. It clearly identifies the returned comparative data (current value, yesterday, 7 days, 30 days, changes, attribution), distinguishing it from a single-point Fear & Greed tool.

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?

It gives an explicit trigger: 'Use when the user asks whether crypto sentiment is improving or worsening.' It does not name sibling tools or state when not to use it, but the usage condition is concrete enough to route most calls correctly.

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