FreeDailyPro Tools

converters_refinance

Read-onlyIdempotent

Refinance break-even calculator: simple and full-cost break-even, interest difference and horizon table

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": {
      "currentBalance": "<currentBalance>",
      "currentRatePct": "<currentRatePct>",
      "newRatePct": "<newRatePct>",
      "newTermYears": "<newTermYears>"
    },
    "name": "converters_refinance"
  }
}

Input Schema

Name	Required	Description
`newRatePct`	Yes	Annual rate of the new loan in percent.
`closingCosts`	No	Closing costs as an amount. Send this or closingCostPct.
`newTermYears`	Yes	Term of the new loan in years.
`closingCostPct`	No	Closing costs as a percent of the current balance.
`currentBalance`	Yes	What you still owe on the current loan.
`currentPayment`	No	Your actual principal-and-interest payment, if you do not want it calculated from balance, rate and time left.
`currentRatePct`	Yes	Current annual rate in percent.
`remainingYears`	No	Years left on the current loan. Send this or remainingMonths.
`remainingMonths`	No	Months left on the current loan.
`plannedYearsToKeep`	No	How long you expect to keep the loan; adds a worthIt answer for that horizon.
`financeClosingCosts`	No	true adds the closing costs to the new loan instead of paying them in cash.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.3/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 safety is covered. The description adds that multiple result sections (simple vs full-cost break-even, interest difference, horizon table) are produced, which is useful given there is no output schema, but it says nothing about defaults, error behavior, or how omitted optional inputs are handled.

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?

A single dense sentence that front-loads the resource and lists the computed outputs with no filler. Nothing to trim.

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 11 parameters and no output schema, the description does well to enumerate the result sections, but it omits how optional inputs default, what the 'worthIt' answer from plannedYearsToKeep means, and units/return shape. Adequate but with clear gaps for a fairly complex calculator.

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 every parameter including the closingCosts/closingCostPct and remainingYears/remainingMonths alternatives is already documented. The description contributes no additional parameter meaning, which is acceptable at this coverage level.

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?

Names a specific resource (refinance break-even) and enumerates the distinct outputs it computes: simple and full-cost break-even, interest difference, and a horizon table. An agent can tell it apart from generic siblings like converters_mortgage or calculate_loan, though the description never explicitly contrasts them.

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?

No statement of when to use this rather than converters_mortgage, converters_amortization, or business_break_even, and no prerequisites or exclusions. The usage is only implied by the tool name and the enumerated outputs.

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

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