Skip to main content
Glama

get_consumer_sentiment_benchmark

Read-only

Live consumer sentiment benchmarks from FRED — University of Michigan sentiment, Conference Board confidence, retail sales, PCE, personal saving rate. Strong/moderate/weak consumer signal for GDP and equity agents. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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

Input Schema

NameRequiredDescriptionDefault
focusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses pricing ($0.10 USDC per call via x402), a concrete failure mode (HTTP 503 with no charge when upstream is unavailable for >50% of fields), and a provenance field (data_source: fred_api/fred_csv/fred_mixed). That is substantive operational context. It loses a point for restating the 503/no-charge condition twice and for not describing the shape of the returned signal.

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 lead sentence is front-loaded with the resource and its component series, and the pricing/failure details follow logically. The 503/no-charge clause is duplicated in near-identical wording, which is wasted space in an otherwise tight definition.

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 does a reasonable job of indicating what is returned (benchmark values plus a strong/moderate/weak signal) and how provenance is exposed. It stops short of describing response structure, units, or how the signal is derived, which leaves some ambiguity for a data-returning 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?

Schema description coverage is 0% for the single 'focus' parameter, so the description must carry the load. It never mentions 'focus' directly, but the enumerated metrics (sentiment, spending via retail sales/PCE, saving rate) map onto the enum values, giving partial implicit meaning. The 'all' option and default behavior remain unexplained.

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 a specific resource and enumerates the underlying series (University of Michigan sentiment, Conference Board confidence, retail sales, PCE, personal saving rate), so an agent knows exactly what data comes back. It does not explicitly contrast itself with siblings like get_inflation_benchmark, but the consumer-sentiment domain is distinct enough to be recognizable.

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

Usage Guidelines3/5

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

It gives a usage hint by naming the audience and purpose ('Strong/moderate/weak consumer signal for GDP and equity agents'), which implies when to reach for it. There is no explicit when-not guidance and no named alternative tool for overlapping macro data, so selection still requires inference.

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