Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_home_vs_rent

Read-onlyIdempotent

Compare the financial outcomes of buying a home versus renting over a chosen period, including yearly costs and break-even analysis.

Instructions

Compare buying vs renting financial outcome.

Use when deciding between buying a home or renting.

Args: home_price: Property price in INR down_payment_percent: Down payment as % loan_interest_rate: Home loan interest rate % loan_tenure_years: Loan tenure monthly_rent: Current monthly rent annual_rent_increase: Expected rent increase %/year expected_property_appreciation: Property appreciation %/year investment_return: Return on invested down payment % analysis_years: Years to compare

Returns: Buy/rent comparison with yearly breakdown and break-even analysis.

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": {
      "home_price": "<home_price>"
    },
    "name": "calculate_home_vs_rent"
  }
}

Input Schema

NameRequiredDescriptionDefault
home_priceYesProperty price in INR
monthly_rentNoCurrent monthly rent in INR
analysis_yearsNoYears to compare
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
investment_returnNoReturn on invested down payment percentage
loan_tenure_yearsNoLoan tenure in years
loan_interest_rateNoHome loan interest rate percentage
annual_rent_increaseNoExpected rent increase percentage/year
down_payment_percentNoDown payment as percentage
expected_property_appreciationNoProperty appreciation percentage/year

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed12 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / analysis_years / title
      Added value: +"Analysis Years"
    • addedInput schema / properties / annual_rent_increase / title
      Added value: +"Annual Rent Increase"
    • addedInput schema / properties / down_payment_percent / title
      Added value: +"Down Payment Percent"
    • addedInput schema / properties / expected_property_appreciation / title
      Added value: +"Expected Property Appreciation"
    • addedInput schema / properties / home_price / title
      Added value: +"Home Price"
    • addedInput schema / properties / investment_return / title
      Added value: +"Investment Return"
    • addedInput schema / properties / loan_interest_rate / title
      Added value: +"Loan Interest Rate"
    • addedInput schema / properties / loan_tenure_years / title
      Added value: +"Loan Tenure Years"
    • addedInput schema / properties / monthly_rent / title
      Added value: +"Monthly Rent"
    • addedInput schema / title
      Added value: +"calculate_home_vs_rentArguments"
    • addedOutput schema / title
      Added value: +"calculate_home_vs_rentDictOutput"
  3. Addedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so safety is covered. The description adds that results include a yearly breakdown and break-even analysis, but discloses nothing about modeling assumptions (maintenance, property tax, transaction costs, loan prepayment) that materially change the comparison. Useful but not rich behavioral context.

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 purpose sentence followed by a usage line, then a structured Args/Returns block. The Args block is largely redundant with the schema, which is mild waste, but the whole thing is short and scannable.

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?

For a 10-parameter financial projection with defaults on 9 of them, an agent needs to know the model's assumptions and default behavior to interpret results correctly; the description covers only inputs and the shape of output. An output schema exists, so return explanation isn't required, but assumption disclosure is missing.

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 schema already documents all parameters, and the Args block largely restates those same descriptions. It adds no units clarification beyond the schema (INR is already there) and omits the schema-only financial_year parameter entirely, so it adds little meaning beyond structured data.

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 opening line states a specific comparison ('Compare buying vs renting financial outcome') with a clear verb and subject, and no sibling tool (calculate_emi, calculate_sip_returns, etc.) overlaps with it. It does not explicitly name a nearest sibling or contrast, but the domain is unambiguous.

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?

The 'Use when deciding between buying a home or renting' line gives a clear decision context for invocation. There are no exclusions or prerequisites, but no sibling offers a competing buy-vs-rent analysis, so the routing gap is minor.

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

Deploy Server

Other Tools