Skip to main content
Glama

get_bls_inflation_components

Read-only

Use when analyzing inflation exposure by spending category, structuring or reviewing vendor contract escalation clauses, benchmarking healthcare or real estate cost inflation, or providing monetary policy context for a CFO or treasury brief. Medical care CPI and housing CPI consistently diverge from headline inflation — critical for healthcare budget planning and commercial lease negotiations. Example: Medical care CPI +3.8% YoY vs headline CPI +3.1% — healthcare costs inflating 23% faster than the general economy, directly driving hospital operating budget overruns in fixed-price service contracts. Source: Bureau of Labor Statistics CPI — the Federal Reserve's primary inflation benchmark. $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoall_items

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 declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: the authoritative source (BLS, the Fed's benchmark), the divergence characteristic of the series, and the explicit $0.10 USDC per-call cost. It omits cadence/recency (monthly release timing) and whether figures are YoY or MoM by default.

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?

Front-loaded with 'Use when...', which is the right structure for a decision-oriented description. The illustrative 3.8% vs 3.1% example and the '23% faster' framing are mildly promotional, but they do convey the use case efficiently. Acceptable length for a data-lookup tool.

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 one optional parameter, an enum, and no output schema, the description covers motivation and sourcing but not the return shape: no mention of period granularity, units, YoY vs MoM, or series history. For a pricing-metered data tool where output structure is undocumented elsewhere, that is a meaningful gap the description should close.

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?

There is a single optional parameter with a self-descriptive enum, but 0% schema description coverage, so the description must carry the semantics. It partially does — medical_care and housing are discussed concretely, and 'spending category' frames the others — but it never explains what 'core_cpi' or 'all_items' mean relative to each other, nor the default behavior when the parameter is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description implies the returned content through examples ('Medical care CPI +3.8% YoY vs headline CPI +3.1%') and names the source ('Bureau of Labor Statistics CPI'), so an agent can infer it returns category-level CPI figures. However, it never states the verb+resource directly — no sentence like 'Returns CPI component series by spending category' — and it does not distinguish itself from the sibling get_inflation_benchmark, leaving the boundary to inference.

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?

Strong, concrete when-to-use guidance: healthcare budget planning, vendor escalation clause review, real estate benchmarking, and CFO/treasury briefings. It explains why the data matters (medical care and housing CPI diverge from headline). It stops short of exclusions or explicitly naming the alternative tool for plain headline inflation, so a 4 rather than 5.

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