AVnester — Indian Real Estate Intelligence

Optimize home-loan tax regime (calculator)

optimize_home_loan_tax_regime

Read-onlyIdempotent

Compare a home-loan borrower's income tax under the OLD vs NEW regime (FY2026-27) and recommend which regime saves more income tax. Pure deterministic slab math — not tax advice. Use when the user asks "old or new tax regime", "home-loan tax benefit", or "section 80C / 24(b) deduction". Models §24(b) interest + §80C principal (+ joint-loan doubling); the response lists benefits it does NOT model (capital gains, HRA, etc.). Always surface the disclaimer field.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ageBand`	No	Taxpayer age band — raises the OLD-regime basic exemption (senior 60–80 → ₹3L, super-senior 80+ → ₹5L). New regime unaffected. Defaults to below60.
`other80C`	No	Other 80C investments in INR (PF, ELSS, insurance, etc.).
`jointLoan`	No	Joint loan with a co-borrower — doubles the 80C/24b caps (equal-split assumption).
`saleValue`	No	NRI only — sale consideration in INR for §195 TDS computation.
`annualRent`	No	Annual rent received in INR — required for let_out.
`isSalaried`	No	Whether the taxpayer is salaried (gets the standard deduction).
`hasForm15CB`	No	NRI only — whether Form 15CB CA-attestation is already in hand.
`indexedCost`	No	NRI only — indexed cost of acquisition (LTCG). When omitted, TDS computed on full sale value.
`annualIncome`	Yes	Annual gross income in INR EXCLUDING house property (salary + other income).
`propertyType`	No	Whether the property is self-occupied or let out.	self_occupied
`holdingMonths`	No	NRI only — holding period in months. ≤24 is STCG; >24 is LTCG.
`nroBalanceUsd`	No	NRI only — NRO account balance in USD equivalent for the repatriation cap math.
`ytdRemittedUsd`	No	NRI only — FY-to-date USD already remitted under the $1M cap.
`residencyStatus`	No	Default resident. Pass nri to get §195 TDS + LRS-cap math in the response.
`homeLoanInterest`	Yes	Annual home-loan interest paid (INR).
`homeLoanPrincipal`	Yes	Annual home-loan principal repaid (INR) — counts toward 80C.
`countryOfResidence`	No	NRI only — DTAA article lookup hint. Free-form country name.
`otherOldRegimeDeductions`	No	Other OLD-regime-only deductions as a lump (HRA exemption, 80D, NPS 80CCD(1B), etc.).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`new`	Yes
`nri`	No
`old`	Yes
`cards`	Yes
`jointLoan`	Yes
`disclaimer`	Yes
`notModeled`	Yes
`assumptions`	Yes
`attribution`	Yes
`recommended`	Yes
`annualIncome`	Yes
`annualSaving`	Yes
`propertyType`	Yes
`residencyStatus`	No
`homeLoanTaxBenefitOld`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate readOnlyHint, idempotentHint, openWorldHint, non-destructive. Description adds that it is pure deterministic math, not tax advice, and lists modelled sections and exclusions. No contradiction.

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?

Three sentences with no extraneous information. Front-loaded with core purpose, followed by usage guidance and behavioral notes. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 18 parameters, output schema exists, and annotations provide safety signals, the description covers the essential behavioral aspects: what is modelled, what is excluded, disclaimer requirement, and usage triggers. Complete for the complexity.

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% with full descriptions for all 18 parameters. The description does not add meaning beyond the schema for individual parameters, but it provides high-level context of what the tool computes. Baseline 3 is appropriate.

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?

Description clearly states the tool compares OLD vs NEW tax regime for home-loan borrowers to recommend the cheaper one, using deterministic slab math. It distinguishes from sibling tools (none of which are tax calculators) by naming specific user queries and tax sections.

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?

Explicitly tells when to use: when user asks 'old or new tax regime', 'home-loan tax benefit', or 'section 80C / 24(b) deduction'. Lists what it does and does not model (capital gains, HRA, etc.), and reminds to surface disclaimer.

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

All AVnester — Indian Real Estate Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: search, details, comparisons (localities vs. listings), and specific financial calculations (EMI, stamp duty, tax, prepayment, balance transfer, decision intelligence). Descriptions clearly differentiate between similar-sounding tools like calculate_home_affordability and get_property_decision_intelligence.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_properties, get_locality_insights, simulate_loan_prepayment). The verbs are descriptive and uniform in style, with no mixed conventions or vague names.

Tool Count5/5

11 tools is well-scoped for a real estate intelligence server, covering property search, locality analytics, and financial calculators. Each tool has a clear purpose and the set feels neither sparse nor bloated.

Completeness5/5

The tool surface covers the full home-buying journey in India: searching properties, getting details, comparing localities/listings, estimating stamp duty and loan payments, optimizing tax regime, simulating prepayment, and assessing overall affordability with decision intelligence. No obvious gaps or dead ends.

Resources

Need Help?