Skip to main content
Glama

Prime Rate, SOFR and Fed Funds Rate Today MCP

Interest rate history

interest_rate_history
Read-onlyIdempotent

History of one reference rate between two dates (up to 5 years per call): start, end, change in basis points, high, low and average, with a daily or sampled table. Rates: sofr, effr, obfr, tgcr, bgcr, sofr_30day_average, sofr_90day_average, sofr_180day_average, sofr_index, fed_funds_upper, prime. EFFR and prime back to 2000, SOFR back to 2018-04-02.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rate": "<rate>"
    },
    "name": "interest_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD. Default today.
rateYesOne of sofr, effr, obfr, tgcr, bgcr, sofr_30day_average, sofr_90day_average, sofr_180day_average, sofr_index, fed_funds_upper, prime.
startNoYYYY-MM-DD. Default 90 days before end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), yet the description still adds real substance: a 5-year maximum span per call, the historical start dates per rate family, and the shape of the result (change in basis points, high, low, average, daily or sampled table). The one soft spot is the unexplained 'sampled table' mode, which has no corresponding parameter in the schema to control it.

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?

Two dense sentences: the first front-loads what the tool returns, the second enumerates accepted rates and their historical coverage. No filler, and the enumeration is placed after the core purpose rather than before it.

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 correctly spends words describing the return payload and the per-rate history depth, which is exactly what an agent needs to judge feasibility. Remaining gaps are minor: no guidance on what happens when a requested range predates the series, and no explanation of how daily vs. sampled output is chosen.

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 coverage is 100% and the schema already documents defaults for start and end and repeats the rate list, so the description mostly parallels structured data. It does add one genuine constraint absent from the schema — the 5-year-per-call limit — but the 'sampled' option it advertises is not represented in any parameter, leaving a gap in how to request it.

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: 'History of one reference rate between two dates', then enumerates the returned statistics and the full rate universe. This clearly distinguishes it from spot-rate siblings like sofr_rate_today or fed_funds_rate_today by scope (range vs. today), though it never names an alternative explicitly.

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?

Usage context is implied rather than stated: the date-range framing and the data-availability notes (EFFR/prime back to 2000, SOFR back to 2018-04-02) tell an agent when the tool applies and when a request will fail for lack of data. There is no explicit 'use this instead of X' routing and no exclusions beyond the 5-year-per-call ceiling.

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.