Skip to main content
Glama

Cash For My Note Calculators

Prepayment-adjusted note value calculator

prepayment_adjusted_value
Read-onlyIdempotent

Prepayments return principal early, which changes a note's value and shortens its life, and this tool prices a fully amortizing mortgage note at your target yield under a constant prepayment rate (CPR) you choose, beside its value with no prepayment and the weighted average life of each. 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": {
      "balance": "<balance>",
      "rate": "<rate>",
      "months": "<months>",
      "yield": "<yield>",
      "cpr": "<cpr>"
    },
    "name": "prepayment_adjusted_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
cprYesConstant prepayment rate you assume, annual % of the balance, e.g. 6. Use 0 for none.
rateYesNote interest rate, annual %, e.g. 7.5.
yieldYesTarget yield the buyer needs, annual % (monthly compounding).
monthsYesNumber of monthly payments LEFT (not the original term).
balanceYesUnpaid principal balance in USD, greater than 0.

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 openWorldHint=false, so the safety profile is covered. The description does add real value beyond that: it discloses the three result categories (CPR value, no-prepayment value, weighted average life) and sets expectations with 'Estimates, not offers or appraisals.' It stops short of describing precision, rounding, or edge-case behavior at cpr=0 or months=1.

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?

One long primary sentence followed by two short qualifiers; nothing is redundant for the reader who needs the disclaimer. The opening clause explaining why prepayments matter is mildly pedagogical and delays the action statement, which is the only reason it falls short of 5.

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 five fully documented required parameters and no output schema, the description does the right extra work by naming the three returned quantities, so an agent knows what comes back without a schema. The disclaimer about being estimates rather than offers also closes the main interpretive risk for a financial calculator.

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%, with every parameter bounded and explained in the schema itself (e.g. months specified as payments LEFT, not original term). The description's mention of 'target yield' and 'a CPR you choose' restates schema content rather than adding syntax, defaults, or units beyond it, so the baseline 3 applies.

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 and resource: it 'prices a fully amortizing mortgage note at your target yield under a constant prepayment rate (CPR)' and returns the comparable no-prepayment value plus weighted average life. That CPR framing clearly separates it from plain pricing tools like note_price or note_yield, though no sibling is named explicitly, which keeps it just 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: an agent can infer it should call this when a prepayment assumption matters, and the cpr schema note ('Use 0 for none') hints at the no-prepayment case. There is no explicit guidance on when to prefer this over the ~20 sibling calculators, nor any stated exclusion or prerequisite.

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