Skip to main content
Glama

Cash For My Note Calculators

Owner financed note calculator

owner_financed_note
Read-onlyIdempotent

An owner-financed (seller-financed) note is the loan a seller carries for the buyer after the down payment, and this tool computes the note amount, monthly payment, loan-to-value at sale, any balloon, and the total of payments and interest. Use it to size a seller-carry note before you sell the property or, later, sell the owner financed note. 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": {
      "sale_price": "<sale_price>",
      "rate": "<rate>",
      "amortization_months": "<amortization_months>"
    },
    "name": "owner_financed_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesNote interest rate, annual %, e.g. 7.5.
sale_priceYesProperty sale price, USD.
down_paymentNoDown payment, USD (or give down_payment_pct). Default 0.
balloon_monthNoMonth the remaining balance is due, if the note has a balloon (optional).
down_payment_pctNoDown payment as % of the sale price (instead of down_payment).
amortization_monthsYesMonths the payment is calculated over, e.g. 360.

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are covered without the description's help. The description adds one genuinely useful behavioral fact — results are estimates, not offers or appraisals — but spends its remaining space on a vendor disclaimer (CashForMyNote.com does not buy notes) that does little for invocation correctness.

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 opening sentence front-loads the definition and the computed outputs before the usage sentence and the disclaimers, so an agent gets the essentials immediately. It is slightly padded by the explanatory 'what is a seller-financed note' phrasing and the trailing corporate disclaimer, but nothing is seriously wasted.

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?

For a six-parameter, non-destructive calculator with no output schema, the description is nearly complete: inputs are fully documented in-schema and the description covers the return values (payment, balloon, LTV, total interest) so the agent knows what it will get back. The only real gap is the absence of any guidance on mutually exclusive down_payment vs down_payment_pct or on which sibling to use for related note questions.

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 one of the six parameters documented in-schema (rate, sale_price, down_payment vs down_payment_pct, balloon_month, amortization_months). The description only implies the down-payment/note-amount relationship ('after the down payment') and adds no format or unit detail beyond what the schema already states, 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?

The description names a specific verb+resource (computes an owner-financed note) and enumerates the exact outputs: note amount, monthly payment, LTV at sale, balloon, total payments and interest. That is far more specific than a tautology, but it never distinguishes itself from close siblings such as balloon_note, note_price or loan_to_value, which an agent must still disambiguate on its own.

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?

It gives two usable contexts — sizing a seller-carry note before a sale, or later when selling the note — which is real when-to-use guidance. It provides no when-not guidance and does not name any alternative tool for the cases where note_price, note_yield or balloon_note would be the better call, so the routing work is left implied.

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