Skip to main content
Glama

get_inflation_benchmark

Read-only

Live inflation benchmarks from FRED — CPI, core CPI, PCE, core PCE, 5Y and 10Y TIPS breakeven expectations, shelter and medical care components. Fed target gap, anchoring signal, and policy implication for macro 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_inflation_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
measureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only/non-destructive/open-world, so the description correctly spends its budget elsewhere: it discloses a paid x402 SLA ($0.10 USDC per call), 503 failure semantics with an explicit no-charge guarantee, and a provenance field (fred_api/fred_csv/fred_mixed). Those are genuinely useful behaviors an agent cannot get from structured fields. The 503 rule is stated twice, which dilutes rather than adds.

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 series list is front-loaded, which is good, but the 503/no-charge clause appears twice in near-identical wording and 'Live source.' is a standalone fragment that adds little after 'Live inflation benchmarks'. The pipe-delimited x402 SLA block reads as appended boilerplate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 useful work by naming the derived metrics (Fed target gap, anchoring signal, policy implication) and the data_source provenance field, so an agent knows roughly what comes back. It is still incomplete on the two things that decide a call: which enum value to send and what happens if none is sent.

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%, so the description must carry the parameter. It partly does by listing the covered series, which maps onto the cpi/pce/breakeven/components enum values, but the 'all' value is never mentioned and the default behavior when 'measure' is omitted (zero required params) is unstated. That leaves a real gap in a one-parameter tool.

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 verb+resource (live inflation benchmarks from FRED) and enumerates the concrete series: CPI, core CPI, PCE, core PCE, 5Y/10Y TIPS breakevens, shelter and medical care. That is far more precise than the bare name. It stops short of differentiating itself from the sibling get_bls_inflation_components, so an agent must still guess which inflation tool to pick.

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?

The only usage signal is the audience phrase 'for macro agents' and an implicit tie to the Fed target gap/anchoring signal framing. There is no explicit when-to-use, no exclusion, and no routing to the closely related get_bls_inflation_components sibling, which an agent would plausibly consider for the same task.

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