Skip to main content
Glama

Payoff plan

payoff_plan
Read-onlyIdempotent

A payoff plan for a car loan, for paying it off early with an extra payment each month: the months and total interest at the regular payment, and with an extra amount toward principal each month (optionally for only the first so many months, or skipping some), with the months and interest the extra saves and the payoff month each way. Give the balance, the APR, and the months left or the regular payment. Lenders differ in how they apply extra payments, and some charge a prepayment penalty.

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>",
      "apr": "<apr>",
      "extra_monthly": "<extra_monthly>"
    },
    "name": "payoff_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
aprYesThe loan APR in percent
balanceYesWhat is owed today
paymentNoThe regular monthly payment; or give months_left instead
months_leftNoPayments left at the regular payment; or give payment instead
skip_monthsNoMonths (1 is the next payment) with nothing extra paid
extra_monthlyYesExtra paid toward principal each month
extra_for_monthsNoPay the extra for only the first this-many months; leave out for every month

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description earns credit for the honest caveat that lenders differ in applying extra payments and some charge a prepayment penalty, which tells the agent results are modeled, not guaranteed. It also sketches the returned figures, though it does not state assumptions (e.g. interest accrual convention, behavior when the payment is too small).

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 core purpose is front-loaded in the opening clause, but the body is one very long sentence with nested parentheticals ('optionally for only the first so many months, or skipping some') that is hard to parse. The lender caveat sits unlinked at the end and the sentence count is minimal yet the density is high; some of it earns its place, some is buried.

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 no output schema, the description does take on the burden of describing return values, and it does: months and interest both ways, the savings, and the payoff month each way. Inputs are covered via required balance/APR/extra_monthly and the payment/months_left alternative. Gaps are minor: no statement of assumptions or edge-case behavior for zero or insufficient extra payments.

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 coverage is 100%, so the baseline is 3. The description restates the either/or of 'months left or the regular payment' and gestures at the skip/first-N-months options, but it adds no semantics beyond what the per-field schema descriptions already say (for example, what skip_months indices mean relative to today, or minimum viable extra_monthly).

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 clearly identifies the resource (a car-loan payoff plan with extra principal payments) and what it computes: months and total interest with and without the extra, plus the payoff month each way. It is specific enough to separate it from neighbors like loan_payment or refinance_check, but it never names a sibling or explicitly contrasts its scope.

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 driving scenario is implicit but discernible: use this when you want to see what an extra monthly principal payment saves on a car loan. 'Give the balance, the APR, and the months left or the regular payment' is input guidance rather than when-to-use guidance, and no alternative tool is named for the overlapping cases (e.g. plain payment math or refinancing).

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