Skip to main content
Glama

AVnester — Indian Real Estate Intelligence

Estimate home-loan EMI (calculator)

calculate_home_affordability
Read-onlyIdempotent

Estimate the monthly home-loan EMI / monthly payment in India — a home-loan calculator. Deterministic math; not advice or a loan-approval claim. Two modes: pass propertyValue (default down payment assumed) OR loanAmount for a specific loan (e.g. "₹50 lakh loan"). Use for "what would my EMI be" / "monthly payment on …". The response assumptionNote states the basis in plain words. 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": {
      "propertyValue": "<propertyValue>"
    },
    "name": "calculate_home_affordability"
  }
}

Input Schema

NameRequiredDescriptionDefault
loanAmountNoLoan amount in INR. Pass this when the user states a specific loan (e.g. "₹50 lakh loan") rather than a property price. Defaults to 80% of propertyValue if omitted.
tenureYearsNoLoan tenure in years. Defaults to 20.
propertyValueYesProperty value (price) in INR. When the user states a property/home price, put it here — an 80% loan is assumed unless loanAmount is also given.
interestRatePercentNoAnnual interest rate (percent). Defaults to current market estimate.

Output Schema

NameRequiredDescriptionDefault
emiYes
cardsYes
disclaimerYes
loanAmountYes
assumptionsYes
attributionYes
tenureYearsYes
totalPaymentYes
totalInterestYes
assumptionNoteYes
inputPropertyValueYes
interestRatePercentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedOutput schema / properties / assumptions / properties / defaultLtvPercent / enum
      Removed value: -[
      -  80
      -]
    • addedOutput schema / properties / assumptions / properties / defaultLtvPercent / type
      Added value: +"number"
    • addedOutput schema / properties / assumptions / properties / lenderMaxLoan
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / assumptions / properties / unfundedAmount
      Added value: +{
      +  "type": "integer"
      +}
    • changedOutput schema / properties / assumptions / required
      Previous value: -[
      -  "defaultLtvPercent",
      -  "actualLtvPercent",
      -  "downPaymentAmount",
      -  "interestType",
      -  "notALoanApproval"
      -]New value: +[
      +  "defaultLtvPercent",
      +  "actualLtvPercent",
      +  "downPaymentAmount",
      +  "lenderMaxLoan",
      +  "unfundedAmount",
      +  "interestType",
      +  "notALoanApproval"
      +]
  2. Changed4 schema fields changed
    • changedInput schema / properties / loanAmount / description
      Previous value: -"Loan amount in INR. Defaults to 80% of propertyValue if omitted."New value: +"Loan amount in INR. Pass this when the user states a specific loan (e.g. \"₹50 lakh loan\") rather than a property price. Defaults to 80% of propertyValue if omitted."
    • changedInput schema / properties / propertyValue / description
      Previous value: -"Property value in INR."New value: +"Property value (price) in INR. When the user states a property/home price, put it here — an 80% loan is assumed unless loanAmount is also given."
    • addedOutput schema / properties / assumptionNote
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "inputPropertyValue",
      -  "loanAmount",
      -  "interestRatePercent",
      -  "tenureYears",
      -  "emi",
      -  "totalInterest",
      -  "totalPayment",
      -  "assumptions",
      -  "attribution",
      -  "disclaimer",
      -  "cards"
      -]New value: +[
      +  "inputPropertyValue",
      +  "loanAmount",
      +  "interestRatePercent",
      +  "tenureYears",
      +  "emi",
      +  "totalInterest",
      +  "totalPayment",
      +  "assumptions",
      +  "assumptionNote",
      +  "attribution",
      +  "disclaimer",
      +  "cards"
      +]
  3. 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: -[
      -  "inputPropertyValue",
      -  "loanAmount",
      -  "interestRatePercent",
      -  "tenureYears",
      -  "emi",
      -  "totalInterest",
      -  "totalPayment",
      -  "assumptions",
      -  "attribution",
      -  "disclaimer"
      -]New value: +[
      +  "inputPropertyValue",
      +  "loanAmount",
      +  "interestRatePercent",
      +  "tenureYears",
      +  "emi",
      +  "totalInterest",
      +  "totalPayment",
      +  "assumptions",
      +  "attribution",
      +  "disclaimer",
      +  "cards"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "assumptions": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "actualLtvPercent": {
      +          "type": "number"
      +        },
      +        "defaultLtvPercent": {
      +          "enum": [
      +            80
      +          ]
      +        },
      +        "downPaymentAmount": {
      +          "type": "integer"
      +        },
      +        "interestType": {
      +          "enum": [
      +            "reducing-balance"
      +          ]
      +        },
      +        "notALoanApproval": {
      +          "enum": [
      +            true
      +          ]
      +        }
      +      },
      +      "required": [
      +        "defaultLtvPercent",
      +        "actualLtvPercent",
      +        "downPaymentAmount",
      +        "interestType",
      +        "notALoanApproval"
      +      ],
      +      "type": "object"
      +    },
      +    "attribution": {
      +      "enum": [
      +        "AVnester"
      +      ]
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "emi": {
      +      "type": "integer"
      +    },
      +    "inputPropertyValue": {
      +      "type": "integer"
      +    },
      +    "interestRatePercent": {
      +      "type": "number"
      +    },
      +    "loanAmount": {
      +      "type": "integer"
      +    },
      +    "tenureYears": {
      +      "type": "integer"
      +    },
      +    "totalInterest": {
      +      "type": "integer"
      +    },
      +    "totalPayment": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "inputPropertyValue",
      +    "loanAmount",
      +    "interestRatePercent",
      +    "tenureYears",
      +    "emi",
      +    "totalInterest",
      +    "totalPayment",
      +    "assumptions",
      +    "attribution",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
  5. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / loanAmount / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / propertyValue / maximum
      Removed value: -9007199254740991
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real context: deterministic output, no advisory standing, and the default assumptions baked into the result. Naming the `assumptionNote` and disclaimer response fields is somewhat redundant with the existing output schema, which keeps this from a 5.

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?

The purpose is front-loaded in the first clause, followed by the caveat and the mode rule in a tight order. It is dense but nearly every sentence carries load; the parenthetical example and the final sentence about the disclaimer field are the only marginal additions.

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 an output schema present, the description needn't enumerate return values, and it correctly limits itself to inputs, defaults, and the non-advisory framing. The one real completeness gap is the unresolved propertyValue-required versus propertyValue-OR-loanAmount tension, which matters for a 4-parameter tool with one required field.

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, and the description does add the useful mode logic (loanAmount overrides the 80% down-payment default). However, it frames the two inputs as an "OR" while the schema marks propertyValue as required in all cases — an agent following the prose could omit propertyValue in loan mode and hit a validation error.

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?

"Estimate the monthly home-loan EMI / monthly payment in India — a home-loan calculator" states a specific verb (estimate) and resource (home-loan EMI) with the geography scoped. It is plainly distinguishable from siblings like optimize_home_loan_tax_regime or simulate_loan_prepayment, which address different questions.

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

Usage Guidelines5/5

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

It gives literal trigger phrasing ("what would my EMI be" / "monthly payment on …") and an explicit routing rule between the two input modes: pass propertyValue for a property price, or loanAmount when the user names a specific loan. It also sets a negative boundary — deterministic math, not advice or an approval claim — so the agent knows not to present output as a lending decision.

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