Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_fear_greed

Retrieve the crypto Fear & Greed index (0–100) with its classification and optional recent readings to gauge market sentiment.

Instructions

Crypto Fear & Greed index (0–100 + classification like Greed/Fear). Uses CMC endpoint /v1/global-metrics/quotes/fear-greed/latest.

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
limitNoHow many recent readings, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden, and it does disclose the data source (CMC endpoint) and the shape/semantics of the returned value (numeric index plus label). It says nothing about rate limits, caching, freshness, or failure behavior, which are the remaining behavioral facts an agent would want for an external-data call.

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 short sentences, front-loaded with what the tool returns, with zero redundant wording. Nothing needs to be trimmed.

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 single-parameter read tool with no output schema, the description adequately covers what comes back (index value plus classification) and the backing endpoint. The only shortfall is that it never touches the `limit` behavior at the description level, though the schema already covers that.

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%, and the single `limit` parameter is already documented in the schema (min 1, max 30, default 1). The description adds no further meaning about how many readings come back or ordering, so baseline 3 applies.

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 the resource precisely (Crypto Fear & Greed index) and even characterizes its output (0–100 plus a classification like Greed/Fear), so an agent knows exactly what it retrieves. It doesn't explicitly contrast itself with siblings, but none of the listed siblings cover this resource, so confusion risk is low.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the alternative ways to obtain sentiment/market context (e.g., get_global_metrics, get_market_brief), and no stated exclusions. The agent must infer applicability purely from the resource name.

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