Skip to main content
Glama

Cash For My Note Calculators

Amortization schedule calculator

amortization_schedule
Read-onlyIdempotent

An amortization schedule shows how each monthly payment splits into interest and principal and what balance is left, and this tool lists it month by month (up to 600 rows) with totals. 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>"
    },
    "name": "amortization_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesNote interest rate, annual %, e.g. 7.5.
rowsNoMax rows. Default 600.
monthsYesNumber of monthly payments.
balanceYesUnpaid principal balance in USD, greater than 0.
paymentNoMonthly payment if not fully amortizing (the last row then clears the remainder).
start_monthNoFirst month to list. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value on output shape (per-month rows capped at 600, plus totals) and on the estimate-only nature of the results. It stops short of describing formatting, rounding, or how non-fully-amortizing payments alter the final row beyond what the schema says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence spends roughly half the text defining what an amortization schedule is, which most agents already know, rather than stating what the tool does for the caller. The remainder is efficient and the estimate disclaimer is worth keeping, but the lead-in could be tightened considerably.

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 a 100%-covered schema, no output schema, and read-only annotations, an agent has nearly everything needed; the description fills the main remaining gap by sketching the returned row structure and totals. Only the absence of routing guidance against the many sibling calculators keeps it from being fully complete.

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 all six parameters — including the optional payment override and start_month — are already documented in structured form. The description contributes nothing parameter-specific beyond repeating the 600-row ceiling, so 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 combination: it 'lists' the interest/principal split and remaining balance 'month by month (up to 600 rows) with totals'. That is concrete enough for an agent to know exactly what comes back. It does not, however, name or contrast itself with siblings such as remaining_balance or loan_payment, so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no reference to any alternative tool. The closing line ('Estimates, not offers or appraisals') functions as a legal disclaimer rather than invocation guidance, so an agent gets no help deciding between this and the other note/loan calculators.

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