Skip to main content
Glama

Cash For My Note Calculators

Land contract payoff calculator

land_contract_payoff
Read-onlyIdempotent

A land contract (contract for deed) payoff is the principal still owed plus interest accrued since the last payment, plus any other charges, and this tool computes that figure for a payoff date using a daily (per-diem) interest rate. Give the principal balance, or the original balance, payment and payments made. 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": {
      "rate": "<rate>",
      "paid_through_date": "<paid_through_date>",
      "payoff_date": "<payoff_date>"
    },
    "name": "land_contract_payoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesNote interest rate, annual %, e.g. 7.5.
paymentNoMonthly payment in USD (principal and interest).
day_countNoDays per year for daily interest: 365 (default) or 360.
payoff_dateYesPayoff date, YYYY-MM-DD.
other_chargesNoLate fees or other amounts owed, USD. Default 0.
payments_madeNoOn-time payments made since the original balance.
original_balanceNoOriginal balance, USD (with payment and payments_made, instead of principal_balance).
paid_through_dateYesDate interest is paid through (usually the last payment date), YYYY-MM-DD.
principal_balanceNoPrincipal owed as of the paid-through date, USD.

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, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral content beyond that: the payoff formula components, the daily per-diem interest basis, and the caveat that results are estimates, not offers or appraisals. It still does not say anything about precision, rounding, or what the result contains.

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 definition is short and front-loads the payoff concept before the input guidance. The closing "CashForMyNote.com does not buy notes or make offers" largely repeats "Estimates, not offers or appraisals" and reads as site boilerplate rather than tool information.

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 9 parameters and no output schema, the description should say what comes back, or at least confirm the result is a single payoff amount versus a breakdown of principal, accrued interest and charges. The input pathways and formula are covered, but the return side is left entirely to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning the per-parameter schema cannot: the two alternative input pathways (principal_balance alone versus original_balance + payment + payments_made), which is a cross-parameter constraint an agent must know to call the tool correctly. The per-diem/day_count dimension is only hinted at rather than explained.

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 the specific concept (land contract / contract for deed payoff) and states the tool computes the principal still owed plus accrued interest plus other charges as of a payoff date using a per-diem rate. That is a concrete verb+resource an agent can match to a request. It does not explicitly distinguish itself from close siblings like remaining_balance or early_payoff_yield, so it stops 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?

It gives input-shape guidance ("Give the principal balance, or the original balance, payment and payments made"), which is useful, but says nothing about when to choose this tool over alternatives such as remaining_balance or early_payoff_yield. Usage is implied by the payoff-date framing rather than stated.

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