Skip to main content
Glama

Cash For My Note Calculators

Early payoff yield calculator

early_payoff_yield
Read-onlyIdempotent

When a note bought at a discount is paid off early, the discount is earned sooner and the yield rises, and this tool computes the yield if the borrower pays off after a chosen number of payments versus holding the note to maturity. Inputs are the price, balance, rate and payment terms you supply. 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": {
      "price": "<price>",
      "balance": "<balance>",
      "rate": "<rate>",
      "months": "<months>",
      "payoff_after_payments": "<payoff_after_payments>"
    },
    "name": "early_payoff_yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesNote interest rate, annual %, e.g. 7.5.
priceYesPrice paid for the note, USD.
monthsYesNumber of monthly payments LEFT (not the original term).
balanceYesUnpaid principal balance in USD, greater than 0.
balloonNoBalloon (lump sum) due with the last payment, USD. Default 0.
paymentNoMonthly payment in USD. If omitted, computed from balance, rate and months.
payoff_after_paymentsYesNumber of payments made before the full payoff.

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 establish that this is a read-only, idempotent, non-destructive, closed-world computation, so the safety profile is covered. The description adds the useful caveat that results are estimates rather than offers or appraisals and that the site does not buy notes, but it says nothing about output format, rounding, or assumptions baked into the model.

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 lead sentence front-loads the concept before the mechanics, and the input sentence follows logically. The two trailing disclaimer sentences are somewhat promotional boilerplate, but they are short and do carry a real limitation about the nature of the result.

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, the description should clarify what comes back; it only says a yield is computed for early payoff versus maturity, leaving the shape of the comparison unspecified. For a seven-parameter calculator this is adequate but leaves the agent guessing about the return structure.

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%, including the important nuance that months is payments remaining rather than original term, so the schema does the heavy lifting. The description only restates the categories of input (price, balance, rate, payment terms) without adding units, defaults, or the price-versus-balance distinction.

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 computation: the yield if a discount-purchased note pays off after a chosen number of payments versus being held to maturity. An agent can tell this is a yield-comparison calculator, though it never names which sibling (e.g. note_yield, prepayment_adjusted_value) it supersedes or differs from.

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 implies the use case (a note bought at a discount being paid off early), which gives an agent a scenario trigger. However, there is no explicit when-not guidance and no mention of the alternative tools to use for straight yield or prepayment value, so the routing decision is left 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.

Resources