Skip to main content
Glama

FinanceQuery

Fear & Greed Index

get_fear_and_greed
Read-onlyIdempotent

Get the CNN Fear & Greed Index — market sentiment from extreme fear (0) to extreme greed (100).

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_and_greed"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint true, so safety and mutability are covered. The description adds the numeric scale semantics, which helps interpret results, but says nothing about update frequency, data source freshness, or what a null/failure looks like.

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?

A single sentence, front-loaded with the verb and resource, with the scale definition appended because it genuinely aids interpretation. No filler.

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 one-parameter, read-only, annotation-rich tool with no output schema, the description covers purpose and value range adequately. The only meaningful gap is lack of guidance on freshness or how to phrase requests that should use this 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?

There is only one optional parameter and schema coverage is 100%, so the schema already explains the comma-separated fields list and its default. The description adds nothing about the parameter, which is acceptable given the schema handles it.

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?

Names a specific verb and resource (Get the CNN Fear & Greed Index) and characterizes the metric's scale from extreme fear (0) to extreme greed (100), so an agent immediately knows what data comes back. It doesn't differentiate from siblings, but no sibling plausibly competes for this function.

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?

The description never states when to reach for this tool, when not to, or what alternatives exist. The agent must infer from the name alone that this is the sentiment gauge to call for market-mood questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.