Compound Mint Money Calculator

Debt payoff calculator

calculate_debt_payoff

Read-onlyIdempotent

Use when a user asks how long it takes to pay off a credit card or loan, what payment clears it by a date, or avalanche vs snowball, e.g. "how long to pay off $5,000 at 24% paying $200 a month?" or "what payment pays off my credit card in 2 years?". One debt: months to pay off and total interest at a monthly payment, or the payment needed to be debt free in target_months. Several debts: send debts (each with name, balance, apr, min_payment) and extra_payment to compare the avalanche and snowball methods.

Input Schema

Name	Required	Description	Default
`apr`	No	Yearly interest rate percent (one debt).
`debts`	No	Several debts, up to 20.
`balance`	No	What you owe in USD (one debt).
`strategy`	No	Several debts: which method (default compare).	compare
`extra_payment`	No	USD a month on top of all minimums (several debts).
`target_months`	No	Months to be debt free (or send monthly_payment).
`monthly_payment`	No	USD paid each month (or send target_months).

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedNov 1, 2026
- addedInput schema / properties / apr / examples
```
Added value: +[
+  18
+]
```
- addedInput schema / properties / apr / maximum
```
Added value: +100
```
- addedInput schema / properties / apr / minimum
```
Added value: +0
```
- addedInput schema / properties / balance / examples
```
Added value: +[
+  10000
+]
```
- addedInput schema / properties / balance / maximum
```
Added value: +100000000
```
- addedInput schema / properties / balance / minimum
```
Added value: +1
```
- addedInput schema / properties / debts / examples
```
Added value: +[
+  [
+    {
+      "apr": 24,
+      "balance": 5000,
+      "min_payment": 150,
+      "name": "Visa"
+    },
+    {
+      "apr": 7,
+      "balance": 12000,
+      "min_payment": 300,
+      "name": "Car loan"
+    }
+  ]
+]
```
- addedInput schema / properties / debts / items / properties / apr / description
```
Added value: +"APR in percent, e.g. 24."
```
- addedInput schema / properties / debts / items / properties / apr / maximum
```
Added value: +100
```
- addedInput schema / properties / debts / items / properties / apr / minimum
```
Added value: +0
```
- addedInput schema / properties / debts / items / properties / balance / description
```
Added value: +"What you owe in USD, e.g. 5000."
```
- addedInput schema / properties / debts / items / properties / balance / minimum
```
Added value: +1
```
- addedInput schema / properties / debts / items / properties / min_payment / description
```
Added value: +"Minimum monthly payment in USD, e.g. 150."
```
- addedInput schema / properties / debts / items / properties / min_payment / minimum
```
Added value: +0
```
- addedInput schema / properties / debts / items / properties / name / description
```
Added value: +"Label, e.g. Visa."
```
- addedInput schema / properties / extra_payment / default
```
Added value: +0
```
- addedInput schema / properties / extra_payment / maximum
```
Added value: +10000000
```
- addedInput schema / properties / extra_payment / minimum
```
Added value: +0
```
- addedInput schema / properties / monthly_payment / maximum
```
Added value: +100000000
```
- addedInput schema / properties / monthly_payment / minimum
```
Added value: +0.01
```
- addedInput schema / properties / strategy / default
```
Added value: +"compare"
```
- addedInput schema / properties / target_months / examples
```
Added value: +[
+  36
+]
```
- addedInput schema / properties / target_months / maximum
```
Added value: +600
```
- addedInput schema / properties / target_months / minimum
```
Added value: +1
```
First observedNov 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by explaining what it computes in each mode (months to payoff, total interest, required payment), though it does not note assumptions like fixed APR or no new charges.

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

Conciseness5/5

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

Front-loaded with the triggering scenario, followed by compact examples and then mode-specific behavior. Every sentence contributes to selection or invocation, with no filler.

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 7-parameter calculator with no output schema, the description covers both operating modes and explains the single-debt return values. The multi-debt output is described only as a comparison of avalanche and snowball, leaving the exact return shape less explicit.

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?

With 100% schema description coverage, the baseline is 3, but the description adds meaningful mode-level semantics: which parameters apply to one debt versus several, and that monthly_payment and target_months are alternatives. It does not explain every parameter beyond the schema, so a 5 is not warranted.

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 with concrete triggers and examples, and clearly separates single-debt from multi-debt operation. It does not explicitly compare itself to any sibling calculator, so the sibling-differentiation bar for a 5 is unmet.

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

Usage Guidelines4/5

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

Opens with explicit 'Use when' conditions and gives user-phrased examples that map directly to the tool. It lacks explicit when-not guidance or named alternatives, but the usage context is otherwise unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Compound Mint Money Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?