Skip to main content
Glama

Prime Rate, SOFR and Fed Funds Rate Today MCP

Prime or SOFR plus margin loan rate

loan_rate_calculator
Read-onlyIdempotent

The all-in variable rate today for a loan priced at an index plus a margin, such as an SBA 7(a) loan at prime + 2.75, a business line of credit at prime + 1 or a commercial loan at 30-day average SOFR + 2.5, with an optional floor or cap and the monthly payment for an amount and term.

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": {
      "index": "<index>",
      "margin_percent": "<margin_percent>"
    },
    "name": "loan_rate_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesThe rate index the loan is priced on.
yearsNoAmortization term in years. Default 10.
amountNoLoan amount in dollars, for a monthly payment.
cap_percentNoRate cap in percent, if the loan has one.
floor_percentNoRate floor in percent, if the loan has one.
margin_percentYesPercentage points over the index, e.g. 2.75.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real behavior: it returns today's live all-in rate and, when amount and term are supplied, a monthly payment, and it applies floor/cap adjustments. It does not disclose where index values come from, how 'today' is determined, or what the response contains when an external rate is unavailable.

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?

Purpose is front-loaded in the opening clause, and the three illustrative loan structures are genuinely useful for recognition. It is a single dense sentence with stacked clauses; trimming one example would improve scannability without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and an openWorld hint, the description carries the burden of explaining returns, and it does so only partially: an all-in rate plus an optional monthly payment. It does not describe response fields, the effective rate date, or the index value actually used, which matter for a live-pricing tool. Enough to call it correctly, not enough to interpret the result confidently.

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 each of the six parameters is already documented, including the margin example and the default term of 10 years. The description reinforces the index-plus-margin relationship and the optionality of floor and cap, but adds no format or edge-case detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific computation: the all-in variable rate for a loan priced at an index plus margin, plus an optional monthly payment. The concrete examples (SBA 7(a) at prime + 2.75, line of credit at prime + 1, commercial loan at 30-day SOFR + 2.5) make the resource unmistakable. It never explicitly distinguishes itself from the index-lookup siblings, so it falls short of a 5.

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 is only implied: the examples show the kinds of loans this applies to, which lets an agent infer that quote-time pricing is the trigger. There is no statement about when to prefer this over sofr_rate_today or fed_funds_rate_today, nor any exclusion or prerequisite. Adequate but leaves routing to inference.

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.