Skip to main content
Glama

get_fomc_rate_probability

Read-only

Use when providing monetary policy narrative context for a macro brief, investment committee, or CFO rate planning session. Returns illustrative cut, hike, and hold probabilities for the next three FOMC meetings based on current FRED fed funds data. Scenario planning tool — not futures-implied market odds. Example: Hold probability 68% at next meeting, cut probability 31% — conditioned on fed funds at 5.33% and latest CPI print. Source: FRED St. Louis Fed. $0.02 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_fomc_rate_probability"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/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), and the description adds substantive behavior beyond them: the data source (FRED St. Louis Fed), the illustrative/non-market-implied caveat, the conditioning inputs (fed funds rate, latest CPI), and a per-call cost of $0.02 USDC. That cost and provenance disclosure is exactly the kind of operational context annotations cannot express.

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 the 'Use when...' trigger, followed by output description, the caveat, an example, and provenance/pricing. Every element earns its place, though the example and the 'Source: FRED' line are somewhat dense in a single block and could be split for scannability.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so with a concrete probability example and the conditioning inputs. Combined with the cost, source, and interpretation caveat, an agent has everything needed to decide to call it and to read the result correctly.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description implicitly confirms this by stating the probabilities are conditioned on current FRED fed funds data and the latest CPI print rather than on caller-supplied inputs, which usefully tells an agent not to look for filtering arguments.

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

Purpose5/5

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

States a specific verb and resource: returns cut, hike, and hold probabilities for the next three FOMC meetings. It also explicitly distinguishes the output from futures-implied market odds, so an agent knows this is a scenario model rather than a market quote. The example ('Hold probability 68% at next meeting, cut probability 31%') pins down the shape of the response.

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?

Opens with an explicit trigger: use when providing monetary policy narrative context for a macro brief, investment committee, or CFO rate planning session. It adds a clear exclusion ('not futures-implied market odds'), which is a meaningful when-not condition. It does not name a sibling alternative to route to when futures-implied odds are actually wanted, so it stops short of full alternatives guidance.

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