Skip to main content
Glama

Cash For My Note Calculators

Mortgage note value calculator

note_price
Read-onlyIdempotent

A mortgage note's value is the present value of its remaining monthly payments (plus any balloon) at the yield a buyer requires, and this tool computes that price. It works the same for mortgage notes, land contracts (contracts for deed), owner-financed notes and other real estate notes. Optionally compares the price with the unpaid balance (discount and % of balance). 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": {
      "months": "<months>",
      "yield": "<yield>"
    },
    "name": "note_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoNote interest rate, annual %. With balance, lets the tool compute the payment at full precision instead of taking payment.
yieldYesTarget yield the buyer needs, annual % (monthly compounding).
monthsYesNumber of monthly payments LEFT (not the original term).
balanceNoUnpaid principal balance in USD, greater than 0.
balloonNoBalloon (lump sum) due with the last payment, USD. Default 0.
paymentNoMonthly payment in USD (principal and interest).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world lookup, so the safety profile is covered. The description adds genuinely useful context beyond that: results are estimates, not offers, and the tool optionally returns a discount and percent-of-balance comparison. It says nothing about rounding, payment-frequency assumptions beyond monthly, or output shape, which keeps this at a 3.

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?

The core definition is front-loaded and the following sentences add scope, the optional comparison, and a disclaimer, with little waste. The opening clause is somewhat long-winded, which keeps it from a 5, but nothing is redundant.

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 carries the burden of describing results, and it does identify the main return (price) plus the optional discount and percent-of-balance comparison. For a read-only six-parameter calculator whose schema is fully documented, this is close to complete, though it could have specified units and precision of the returned price.

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 description coverage is 100%, so every parameter including remaining months, yield, rate, payment and balloon is already documented in the schema. The description reinforces the conceptual model (present value of remaining payments plus balloon at the required yield) but adds no format, default or combination rules beyond what the schema states. Baseline 3 is appropriate.

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 verb and resource: it computes the present value (price) of a mortgage note from its remaining monthly payments plus any balloon at a buyer-required yield. It also broadens scope to land contracts, contracts for deed and owner-financed notes. It stops short of naming which sibling to use instead, so a note_discount or payment_stream_value comparison is left to inference.

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 implied by the definition of the calculation (give remaining months, a yield, and either payment or balance+rate), but there is no explicit when-to-use or when-not-to-use guidance versus the many pricing siblings. The one clear boundary statement is that output is an estimate, not an offer or appraisal.

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