Skip to main content
Glama

Stratalize Intelligence

Get Fomc Rate Probability

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

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

Annotations only say readOnly/openWorld/non-destructive, but the description adds the material caveats: the numbers are illustrative rather than market-implied, they are conditioned on stated fed funds and CPI inputs, they cover exactly the next three meetings, the data source is FRED St. Louis Fed, and each call costs $0.02 USDC. The cost disclosure and the accuracy caveat are exactly the kind of context annotations cannot convey.

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 when-to-use clause, then the return content, then the caveat, example, source, and price. Every sentence carries information, though the list is dense enough that the central caveat ('not futures-implied market odds') would land harder if it were not stacked mid-paragraph.

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 must carry the return shape, and it does: three meetings, three outcome probabilities, an illustrative example, and the conditioning basis. It leaves open update cadence and time horizon (e.g., how stale the FRED data may be), which matters for a rate-probability tool but is a modest gap.

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 there is no parameter semantics to add beyond the baseline. The description does clarify that the conditioning inputs (fed funds rate, latest CPI print) are fixed internally rather than caller-supplied, which usefully answers why no arguments are accepted.

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?

The description names a specific verb and resource: it 'returns illustrative cut, hike, and hold probabilities for the next three FOMC meetings based on current FRED fed funds data.' That is a concrete, unambiguous output scope, and the 'not futures-implied market odds' clause separates it from market-implied alternatives an agent might otherwise assume.

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?

It gives an explicit use context ('monetary policy narrative context for a macro brief, investment committee, or CFO rate planning session') plus an explicit exclusion ('Scenario planning tool — not futures-implied market odds'). What is missing is a named in-catalog alternative to route to when futures-implied odds are actually wanted, so the negative guidance is not fully actionable.

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