Skip to main content
Glama

Prime Rate, SOFR and Fed Funds Rate Today MCP

Fed rate cuts and hikes

fed_rate_changes
Read-onlyIdempotent

Every change to the federal funds target since a date (default the last 5 years, back to 2000): the date it took effect, cut or hike, basis points, the new target range and the prime rate after it. Answers "when did the Fed last cut rates".

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": "fed_rate_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoYYYY-MM-DD, back to 2000-07-03. Default 5 years ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds real behavioral context beyond them by spelling out the returned fields and the data-availability floor, which matters for interpreting results, though the default-window and 2000 floor partially duplicate the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states scope, returns, then limits, followed by a compact example question. No filler.

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?

For a one-optional-parameter read tool with no output schema, the description covers purpose, default, data floor, and return fields, so an agent can call it and interpret results without extra information.

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?

Only one optional parameter with 100% schema coverage, so the schema already documents the YYYY-MM-DD format, the 2000-07-03 floor, and the 5-year default. The description restates the same default and range without adding new syntax or semantics.

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?

States a specific verb+resource: 'Every change to the federal funds target since a date', and enumerates exactly what is returned (date, cut/hike, basis points, new target range, prime rate). This is easy to separate from a 'rate today' tool, though no sibling is named explicitly.

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?

Gives clear usage context via the example question 'when did the Fed last cut rates' and states the default window (5 years) and hard floor (back to 2000). No when-not-to-use condition or named alternative is given.

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.