Skip to main content
Glama

Cash For My Note Calculators

Note rate vs current mortgage rates

rate_vs_market
Read-onlyIdempotent

A note whose rate is below current mortgage rates usually sells at a deeper discount, and this tool gives the gap in percentage points between a note's rate and the latest weekly 30-year fixed mortgage average (Freddie Mac PMMS), with that week's date. Estimates, not offers or appraisals. CashForMyNote.com does not buy notes or make offers.

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": {
      "note_rate": "<note_rate>"
    },
    "name": "rate_vs_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_rateYesNote interest rate, annual %, e.g. 7.5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context, which it does: it discloses the external data source (Freddie Mac PMMS), the weekly refresh cadence, that the response carries the reference week's date, and that outputs are estimates with no purchase or offer implied. It stops short of stating the sign convention of the gap (note minus market, or the reverse), which is the one behavioral detail left ambiguous.

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 sentences with zero filler: the first frames why the comparison matters and then immediately defines the returned quantity and its provenance; the second is a tight, necessary disclaimer. The key computation is front-loaded rather than buried.

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 one required parameter, no output schema and full annotation coverage, the description is close to self-sufficient: it explains what is computed, where the benchmark comes from, how fresh it is, and what the result is not. The only material omission is the direction/sign of the percentage-point gap and any note about data lag or availability.

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% on the single note_rate parameter, so the schema already documents type, bounds, units and an example; the description adds no syntax, format or edge-case detail beyond it. Baseline 3 applies 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise computation: the gap in percentage points between a note's rate and the latest weekly 30-year fixed mortgage average, plus the week's date, and names the data source (Freddie Mac PMMS). An agent can tell this apart from a raw rate-listing sibling such as market_rates because the output is a differential, not the average itself.

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?

The opening clause supplies the motivation for calling it (below-market notes sell at deeper discounts), which implies when it is useful, and the closing disclaims that results are estimates rather than offers or appraisals. However, it never names an alternative tool or states when a different rate-comparison tool should be preferred, so guidance is implied rather than explicit.

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