Skip to main content
Glama

Prime Rate, SOFR and Fed Funds Rate Today MCP

SOFR rate today

sofr_rate_today
Read-onlyIdempotent

The latest Secured Overnight Financing Rate (SOFR) with the change from the previous business day, percentiles and volume, the 30, 90 and 180 day SOFR averages and SOFR Index (used to price SOFR loans), and the other New York Fed reference rates: TGCR, BGCR, OBFR and EFFR.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds substantive context beyond that: what fields are returned, that the change is measured against the previous business day, and that the SOFR Index is used to price SOFR loans. It does not discuss update cadence, holiday behavior, or failure modes, which keeps it short of a 5.

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?

It is a single sentence that front-loads the primary resource (SOFR) and its headline values before listing secondary outputs. Every clause corresponds to actual returned data, so nothing is filler, though the tail ('the other New York Fed reference rates: TGCR, BGCR, OBFR and EFFR') is dense ticker listing that could be tightened.

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 bears the burden of describing return content, and it does so thoroughly for a zero-argument fetch. Missing only operational details an agent might want, such as publication timing and whether the snapshot is always the current business day.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing parameter-like concepts (date ranges, rate type selectors) that would confuse the caller.

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?

The description names a specific resource (SOFR) and enumerates precisely what is returned: current rate, change vs. prior business day, percentiles, volume, 30/90/180-day averages, SOFR Index, plus TGCR, BGCR, OBFR and EFFR. It is a noun-phrase data inventory rather than an explicit verb, but an agent can tell exactly what data this tool surfaces. It does not distinguish itself from siblings such as fed_funds_rate_today or interest_rate_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no sentence telling the agent when to use this tool versus fed_funds_rate_today or interest_rate_history, and no exclusions (e.g., 'for historical series use interest_rate_history'). The temporal scope is only implied by the name/title 'today' and the word 'latest'. A sibling with clear overlap exists, so the absence of routing guidance is a real gap.

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.