Skip to main content
Glama

AVnester — Indian Real Estate Intelligence

Compare home-loan balance transfer (calculator)

compare_balance_transfer
Read-onlyIdempotent

Compare staying on your current home loan vs. transferring (refinancing) to a lower rate. Pure deterministic math — no advice, no loan-approval claim. Use when the user asks "should I switch lenders / transfer my loan / refinance". Returns new EMI, interest saved over the remaining tenure, switching cost, net saving, and the breakeven month. Includes a disclaimer field to show.

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": {
      "outstandingPrincipal": "<outstandingPrincipal>",
      "currentRatePercent": "<currentRatePercent>",
      "newRatePercent": "<newRatePercent>",
      "remainingTenureYears": "<remainingTenureYears>"
    },
    "name": "compare_balance_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
flatCostsNoFlat legal + valuation charges in INR. Defaults to ₹12,500.
newRatePercentYesNew lender annual interest rate (percent).
processingFeePctNoNew-lender processing fee on the balance (percent). Defaults to 0.5%.
currentRatePercentYesCurrent annual interest rate (percent).
outstandingPrincipalYesCurrent outstanding home-loan principal in INR.
remainingTenureYearsYesYears left on the loan.

Output Schema

NameRequiredDescriptionDefault
cardsYes
notesNo
newEmiYes
worthItYes
netSavingYes
currentEmiYes
disclaimerYes
assumptionsYes
attributionYes
switchingCostYes
newRatePercentYes
breakevenMonthsYes
monthlyEmiSavingYes
newTotalInterestYes
currentRatePercentYes
grossInterestSavedYes
currentTotalInterestYes
outstandingPrincipalYes
remainingTenureYearsYes
breakevenWithinTenureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / breakevenWithinTenure
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / notes
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / cards
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "data": {
      +        "additionalProperties": {},
      +        "type": "object"
      +      },
      +      "priority": {
      +        "type": "integer"
      +      },
      +      "template": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "template",
      +      "data",
      +      "priority"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "outstandingPrincipal",
      -  "currentRatePercent",
      -  "newRatePercent",
      -  "remainingTenureYears",
      -  "currentEmi",
      -  "newEmi",
      -  "monthlyEmiSaving",
      -  "currentTotalInterest",
      -  "newTotalInterest",
      -  "grossInterestSaved",
      -  "switchingCost",
      -  "netSaving",
      -  "breakevenMonths",
      -  "worthIt",
      -  "assumptions",
      -  "attribution",
      -  "disclaimer"
      -]New value: +[
      +  "outstandingPrincipal",
      +  "currentRatePercent",
      +  "newRatePercent",
      +  "remainingTenureYears",
      +  "currentEmi",
      +  "newEmi",
      +  "monthlyEmiSaving",
      +  "currentTotalInterest",
      +  "newTotalInterest",
      +  "grossInterestSaved",
      +  "switchingCost",
      +  "netSaving",
      +  "breakevenMonths",
      +  "worthIt",
      +  "assumptions",
      +  "attribution",
      +  "disclaimer",
      +  "cards"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "assumptions": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "floatingForeclosurePenaltyWaived": {
      +          "enum": [
      +            true
      +          ]
      +        },
      +        "interestType": {
      +          "enum": [
      +            "reducing-balance"
      +          ]
      +        },
      +        "notALoanApproval": {
      +          "enum": [
      +            true
      +          ]
      +        },
      +        "tenureHeldConstant": {
      +          "enum": [
      +            true
      +          ]
      +        }
      +      },
      +      "required": [
      +        "interestType",
      +        "tenureHeldConstant",
      +        "floatingForeclosurePenaltyWaived",
      +        "notALoanApproval"
      +      ],
      +      "type": "object"
      +    },
      +    "attribution": {
      +      "enum": [
      +        "AVnester"
      +      ]
      +    },
      +    "breakevenMonths": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "currentEmi": {
      +      "type": "integer"
      +    },
      +    "currentRatePercent": {
      +      "type": "number"
      +    },
      +    "currentTotalInterest": {
      +      "type": "integer"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "grossInterestSaved": {
      +      "type": "integer"
      +    },
      +    "monthlyEmiSaving": {
      +      "type": "integer"
      +    },
      +    "netSaving": {
      +      "type": "integer"
      +    },
      +    "newEmi": {
      +      "type": "integer"
      +    },
      +    "newRatePercent": {
      +      "type": "number"
      +    },
      +    "newTotalInterest": {
      +      "type": "integer"
      +    },
      +    "outstandingPrincipal": {
      +      "type": "integer"
      +    },
      +    "remainingTenureYears": {
      +      "type": "integer"
      +    },
      +    "switchingCost": {
      +      "type": "integer"
      +    },
      +    "worthIt": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "outstandingPrincipal",
      +    "currentRatePercent",
      +    "newRatePercent",
      +    "remainingTenureYears",
      +    "currentEmi",
      +    "newEmi",
      +    "monthlyEmiSaving",
      +    "currentTotalInterest",
      +    "newTotalInterest",
      +    "grossInterestSaved",
      +    "switchingCost",
      +    "netSaving",
      +    "breakevenMonths",
      +    "worthIt",
      +    "assumptions",
      +    "attribution",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
  4. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / flatCosts / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / outstandingPrincipal / maximum
      Removed value: -9007199254740991
  5. Added

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the math is deterministic, it gives no advice and makes no approval claim, and it carries a disclaimer field the caller should surface. Annotations already cover read-only/idempotent/non-destructive, so this extra framing is what earns credit; the only omission is any note on input validation or edge-case handling.

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?

Three compact sentences: purpose first, then usage trigger, then return contract. The middle sentence is slightly repetitive in restating 'no advice, no loan-approval claim' alongside the disclaimer mention, but there is no filler overall.

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 6-parameter read-only calculator with a full schema and an output schema, the definition covers purpose, trigger, deterministic nature, and disclaimer obligation. Nothing essential is missing, though a note on how switching cost is composed from the optional fee parameters would close the last gap.

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%, including defaults for flatCosts (₹12,500) and processingFeePct (0.5%), so the description need not carry parameter meaning. The description's list of return values (EMI, interest saved, switching cost, breakeven month) is output information, not parameter guidance, and an output schema already exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific comparison ('staying on your current home loan vs. transferring (refinancing) to a lower rate') with a concrete decision framing, which cleanly separates it from siblings like simulate_loan_prepayment or calculate_home_affordability.

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?

Gives an explicit trigger with quoted user phrasings ('should I switch lenders / transfer my loan / refinance'), so the agent knows when to select it. It does not name a competing tool or state when not to use it, so it stops short of full routing guidance.

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