Skip to main content
Glama

How much home loan can I afford?

home_loan_affordability
Read-onlyIdempotent

Largest home loan a monthly take-home pay supports, the way Indian banks work it out: all EMIs together within a share of take-home pay (FOIR, default 50%), and RBI's loan-to-value limits (90% of the home's value up to Rs 30 lakh, 80% up to Rs 75 lakh, 75% above). Optionally checks whether a given home price fits, with the EMI and down payment. Stamp duty and registration (about 6-8%) are extra and not financed.

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": {
      "monthly_take_home_pay": "<monthly_take_home_pay>"
    },
    "name": "home_loan_affordability"
  }
}

Input Schema

NameRequiredDescriptionDefault
home_priceNoOptional: price of a home to check, in rupees, without stamp duty
tenure_yearsNoLoan tenure in years (default 20)
emi_share_percentNoShare of take-home pay all EMIs may use, % (default 50; banks allow about 50-60%)
annual_interest_rateNoHome loan rate, % per year (default 8.5)
existing_monthly_emisNoOther EMIs already being paid each month, in rupees (default 0)
monthly_take_home_payYesMonthly take-home (net) pay in rupees

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), so the description's job is domain context — and it delivers: FOIR default of 50%, the RBI LTV tiers of 90/80/75%, and the caveat that stamp duty and registration of about 6-8% are extra and not financed. It also indicates what the optional path returns (EMI and down payment), though it does not describe the response shape for the base case.

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?

Front-loaded with the core answer and then the method, so an agent gets the gist in the first clause. It is dense — one long paragraph with several parenthetical rules — which costs some readability but contains little filler.

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 tool with no output schema and non-trivial regulatory logic, the description supplies the formulas, defaults and the stamp-duty exclusion an agent needs to interpret inputs. The remaining gap is that the return payload for the non-home_price case (just a max amount, or a breakdown?) is not stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description nonetheless adds meaning: it explains the FOIR concept behind emi_share_percent (with the real-world 50-60% bank range), ties home_price to the LTV slabs, and warns that the price should exclude stamp duty. This goes beyond restating schema text.

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?

States a precise verb+resource: computes the largest home loan a given monthly take-home pay supports. The affordability framing (max principal from income) inherently separates it from EMI/interest calculators like calculate_loan_emi, and it names the exact domain rules used (FOIR, RBI LTV slabs).

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?

Implied usage is clear enough (call it with take-home pay; optionally add home_price to test affordability), and it clarifies that the home-price check is optional. But it never states when to prefer this over calculate_loan_emi or rent_vs_buy_calculator, nor lists prerequisites such as income being net rather than gross beyond the schema's own wording.

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