Skip to main content
Glama

Rent vs Buy

rent_vs_buy_calculator
Read-onlyIdempotent

Buy a home or keep renting? See which leaves you richer. Same calculation as https://paisafinder.com/calculators/rent-vs-buy-calculator. Every input is optional; anything left out uses the default shown in its schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rent_vs_buy_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
downNoDown payment (%). Banks lend up to 75-90% of the price
rateNoHome loan rate (%)
rentNoMonthly rent for a similar home (rupees)
priceNoHome price (rupees)
stampNoStamp duty + registration (%). Paid once at purchase; 5-8% in most states
yearsNoYears you plan to stay (years)
tenureNoLoan tenure (years)
upkeepNoUpkeep (per year, % of price). Maintenance, property tax, insurance, repairs; rises with rent
rentHikeNoRent increase (per year) (%)
invReturnNoReturn on invested money (%). What the renter earns on the down payment and the monthly savings
appreciationNoHome price growth (per year) (%). Indian homes: about 4-6% a year over the last decade

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's added value is the note that every input is optional and omitted values fall back to schema defaults, plus the parity claim against the public calculator URL. What is missing is any statement of the shape of the result — whether it returns a rupee difference, a break-even year, or a verdict — which is the main behavioral unknown for a simulation tool.

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 short sentences, front-loaded with the decision the tool answers and followed by the defaulting rule, with no filler. The external URL is the weakest sentence and could be dropped without loss for an agent, but overall the text is tight.

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, zero required fields, and no output schema, the description should at minimum say what comes back and in what form; it does not. The defaulting behavior is covered, but an agent still cannot tell whether the response is a single number, a break-even horizon, or a side-by-side comparison.

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 each of the 11 parameters already carries its unit, range, and default, and the baseline of 3 applies. The description only adds the omission rule ('anything left out uses the default shown in its schema'), which is a real but small increment over the schema and does not explain how inputs interact (e.g., that invReturn applies to the renter's down payment and monthly savings).

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?

The description states a specific decision problem (buy vs. rent) and a specific outcome (which leaves you richer), which is enough to distinguish it from every numeric sibling like calculate_loan_emi or flat_vs_reducing_rate_calculator. It falls short of a 5 because it phrases the purpose as a rhetorical question rather than a direct verb+resource statement of what is computed.

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?

The framing 'Buy a home or keep renting?' implies the scenario in which the tool applies, but there is no explicit when-to-use guidance, no exclusions, and no pointer to related tools (e.g., calculate_loan_emi for the loan leg alone). Usage is inferable rather than stated.

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