Skip to main content
Glama

Stratalize Intelligence

Get Inflation Benchmark

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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), yet the description adds genuinely non-obvious behavior: a per-call price of $0.10 USDC, the exact failure contract (HTTP 503 with no charge when upstream is unavailable or >50% of fields are missing), and a data_source provenance field with enumerated values. The main flaw is that the 503/no-charge statement is repeated twice in slightly different wording, which wastes space and slightly muddies an otherwise strong disclosure.

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 opening is well front-loaded with the concrete data list, but the tail degrades into a run-on mix of marketing fragments ('Live source.', 'policy implication for macro agents'), a pipe-delimited pricing note, and a duplicated 503/no-charge sentence. Roughly a third of the text could be cut without losing information.

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 benchmark tool with no output schema, the description covers the essentials: what data comes back, provenance signaling via data_source, cost, and error semantics. It stops short of describing result shape or units (e.g., percent vs index level), which matters somewhat for numeric benchmarks, but the annotations and lack of output schema lower the bar.

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 carries the parameter burden, and the measure enum values are only indirectly reflected: the prose lists the underlying series (cpi, pce, breakeven, components) but never maps them to the enum, never explains what 'all' does, and never states that measure is optional and what the default is. It adds real meaning about what each measure contains, but not enough to make invocation unambiguous on the first try.

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 (FRED inflation benchmarks) and enumerates the concrete measures returned: CPI, core CPI, PCE, core PCE, 5Y/10Y TIPS breakevens, shelter and medical care components, plus derived Fed target gap and anchoring signal. That is far more specific than the title alone. It does not, however, distinguish itself from the sibling get_bls_inflation_components, which an agent could plausibly confuse with the shelter/medical-care component coverage mentioned here.

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 phrase 'for macro agents' implies the intended audience and use case, and the listed measures hint at scenario selection, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer on its own whether to call this versus get_bls_inflation_components for component-level data.

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