Skip to main content
Glama

Leeway Financial Data

sentiment

sentiment
Read-only

Market sentiment. family is breadth, breadth_volume, naaim, fear_index, smart_money, cot, or sce. For breadth, breadth_volume, cot, and sce, omit series to list the catalog and pass series to read one. breadth and breadth_volume take a symbol from their catalog such as US500 or DEU40. cot and sce take the id from the catalog. naaim, fear_index, and smart_money are single series, so omit series. from and to are YYYY-MM-DD and apply to one series. cot filters active, set, contract, and report apply only when series is omitted. Free access is delayed: the newest points are omitted, and the response includes pointsRemoved and remedy_url. Costs 1 request unit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "family": "<family>"
    },
    "name": "sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD
setNoPass all to list every stored series
fromNoFirst date, YYYY-MM-DD
activeNotrue (default), false, or all
familyYesWhich sentiment series.
reportNodisagg, tff, or legacy
seriesNoBreadth symbol or series id. Omit to list the catalog. Omit for naaim, fear_index, and smart_money.
contractNoOne CFTC market code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / series / description
      Previous value: -"Index symbol or series id. Omit to list the catalog. Omit for naaim, fear_index, and smart_money."New value: +"Breadth symbol or series id. Omit to list the catalog. Omit for naaim, fear_index, and smart_money."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that free access is delayed with the newest points omitted, that the response carries pointsRemoved and remedy_url, and that the call costs 1 request unit. This is exactly the kind of truncation and cost context an agent cannot get from structured fields.

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 catalog-vs-read rule is front-loaded and every sentence carries operational information with no filler. The tradeoff is telegraphic phrasing ('cot filters active, set, contract, and report apply only when series is omitted') that is dense but slightly hard to parse on first read.

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?

For an 8-parameter tool with no output schema, the description covers catalog enumeration, symbol/id selection per family, date format, filter applicability, and response truncation behavior. An agent has everything needed to construct a correct call without trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description still adds real meaning: which families accept a symbol versus an id, that from/to apply to a single series, and that active/set/contract/report are only meaningful when series is omitted. Those conditional rules are not encoded in the schema and materially change how the parameters must be set.

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 opens with 'Market sentiment' and enumerates the seven families, so the resource is unambiguous and clearly distinct from the price/macro/fundamentals siblings. It never uses an explicit verb like 'get' or 'list', leaving the agent to infer retrieval, which keeps it just short of a 5.

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 concrete selection logic: omit series to list the catalog, pass series to read one, omit series entirely for naaim/fear_index/smart_money, and use symbol vs id depending on family. The gap is that it never explains when to reach for this tool instead of a sibling such as prices or macro, nor any exclusions.

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.

Resources