CEV-OS Data API

Stock Sentiment Gauge

get_stock_sentiment

Read-onlyIdempotent

Use this when you need a 0-100 US stock-market fear/greed reading with its eight component percentiles and recent daily history (cev-os's own index; IEX ETF closes + US Treasury yields). Free. License: cleared_with_attribution. Attribution required: Data provided for free by IEX. By accessing or using IEX Historical Data, you agree to the IEX Historical Data Terms of Use. IEX Historical Data Terms of Use: https://www.iex.io/legal/hist-data-terms 10-year yield: U.S. Department of the Treasury, Daily Treasury Par Yield Curve Rates. Index: CEV-OS Stock Sentiment Gauge (cev-os).

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

Input Schema

Name	Required	Description	Default
`days`	No	Days of history to return (1-60, default 30).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, and idempotent behavior. The description adds useful context beyond annotations: the index construction, data sources (IEX ETF closes and Treasury yields), free access, and mandatory attribution terms. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and useful for tool selection, but the description is significantly lengthened by legal attribution boilerplate that does not help an agent choose or invoke the tool. It remains structured but is not tightly concise.

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?

With no output schema, the description explains the return content: a 0-100 reading, eight component percentiles, and daily history. Combined with annotation coverage and a fully described single parameter, this is largely complete, though it could specify output field structure more precisely.

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?

The single parameter `days` is fully documented in the schema with range and default. The description says 'recent daily history' but does not add syntax or behavioral detail beyond the schema, so the baseline of 3 is appropriate.

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 clearly states that it returns a 0-100 US stock-market fear/greed reading with eight component percentiles and recent daily history, plus its data sources. It is specific about the metric and scope, but does not explicitly distinguish it from sibling tools such as get_market_mood.

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 a clear usage condition: 'Use this when you need a 0-100 US stock-market fear/greed reading...' No when-not guidance or named alternatives are provided, but the context for use is explicit.

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

All CEV-OS Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?