FreeDailyPro Calculators

converters_loan_interest

Read-onlyIdempotent

Loan and interest calculator: loan payments, simple interest and compound interest with contributions in one endpoint

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": {
      "kind": "<kind>"
    },
    "name": "converters_loan_interest"
  }
}

Input Schema

Name	Required	Description
`fee`	No	Loan: upfront fee; adds the APR and money received.
`kind`	Yes	loan: payment, schedule and solving; simple-interest; compound-interest (with regular contributions and inflation).
`years`	No	Term in years.
`payment`	No	Loan: target payment per period for solveFor amount, term or rate.
`loanType`	No	Loan: amortized (default), deferred or zeroCoupon.
`solveFor`	No	Loan: what to solve for; amount, term and rate need 'payment'.
`frequency`	No	Compound interest: compounding frequency (default annually).
`principal`	No	Amount. For kind loan it is required except when solveFor is 'amount'.
`startDate`	No	Interest kinds: start date, YYYY-MM-DD; adds the maturity date.
`compounding`	No	Loan: how interest compounds (default: on every payment).
`extraMonthly`	No	Plain monthly loan: extra principal each month; adds interest saved and payments saved.
`inflationPct`	No	Compound interest: adds the future value in today's dollars.
`previewMonths`	No	Loan: number of schedule rows to return, 0 to 12.
`yearlySummary`	No	Plain monthly loan: adds a year-by-year principal, interest and balance table.
`firstPaymentDate`	No	Loan: date of the first payment, YYYY-MM-DD; adds payment dates and the payoff date.
`paymentFrequency`	No	Loan: payment frequency (default monthly).
`annualRatePercent`	No	Annual rate in percent.
`contributeAtStart`	No	Compound interest: true adds each contribution at the start of the month instead of the end.
`compareWithCompound`	No	Simple interest: adds the result with annual compounding for comparison.
`monthlyContribution`	No	Compound interest: amount added every month (needs frequency monthly).

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 3, 2026
- addedInput schema / properties / annualRatePercent / minimum
```
Added value: +0
```
- addedInput schema / properties / extraMonthly / minimum
```
Added value: +0
```
- addedInput schema / properties / fee / minimum
```
Added value: +0
```
- addedInput schema / properties / monthlyContribution / minimum
```
Added value: +0
```
- addedInput schema / properties / payment / minimum
```
Added value: +0
```
- addedInput schema / properties / previewMonths / minimum
```
Added value: +0
```
- addedInput schema / properties / principal / minimum
```
Added value: +0
```
- addedInput schema / properties / years / minimum
```
Added value: +0
```
AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without prose. The description adds only that this is a single-endpoint pure calculation covering three modes and that compound interest accepts contributions; it says nothing about output shape per mode or the response additions (schedules, interest saved, payoff dates) that the schema parameters allude to.

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?

It is a single front-loaded sentence with no filler, and the three mode names come first so an agent can scan them immediately. For a tool with 20 parameters and three distinct modes, one sentence is lean but not padded.

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?

There is no output schema, so the description would normally need to explain return values; here the rich per-parameter schema descriptions (which state what each flag 'adds' to the response) largely compensate. The main gap is that the description never explains that the response differs substantially by 'kind' or that required fields vary by mode.

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% and the schema documents every one of the 20 parameters, including enum meanings, defaults, and cross-field conditions. The description adds no parameter-level information 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 the resource (loan and interest calculations) and the three concrete operations covered: loan payments, simple interest, and compound interest with contributions. The phrase 'in one endpoint' hints that it consolidates the three sibling calculators (calculate_loan, calculate_simple_interest, calculate_compound_interest), but it never names them, so the differentiation is only implied.

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?

Usage is only inferable: the three modes in the description map to the 'kind' enum, so an agent can deduce that this tool is the umbrella for all three calculation types. There is no explicit statement of when to prefer it over the dedicated sibling calculators, and no guidance on mode-specific prerequisites (e.g. that solveFor 'amount'/'term'/'rate' require a payment).

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

All FreeDailyPro Calculators 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?