Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020

calculate_home_vs_rent

Read-onlyIdempotent

Compare the financial outcomes of buying a home versus renting. Input property price, down payment, loan details, rent, and investment returns to determine which option is more cost-effective over time.

Instructions

Compare buying vs renting financial outcome.

Use when deciding between buying a home or renting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
home_priceYesProperty price in INR
down_payment_percentNoDown payment as percentage
loan_interest_rateNoHome loan interest rate percentage
loan_tenure_yearsNoLoan tenure in years
monthly_rentNoCurrent monthly rent in INR
annual_rent_increaseNoExpected rent increase percentage/year
expected_property_appreciationNoProperty appreciation percentage/year
investment_returnNoReturn on invested down payment percentage
analysis_yearsNoYears to compare

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations provide readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds no extra behavioral details (e.g., assumptions, output specifics), but given annotations cover the key aspects, a 3 is appropriate.

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?

Two sentences with zero wasted words – 'Compare buying vs renting financial outcome. Use when deciding between buying a home or renting.' Every sentence adds value.

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?

The tool has an output schema (not shown but present), so return values are documented. The description covers the main purpose and usage. It could mention the output type briefly, but with high schema coverage and annotations, it's nearly complete.

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 all parameters have individual descriptions. The tool description does not add extra semantic meaning beyond the schema; it only gives a general overview. Baseline 3 is correct.

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?

The description clearly states 'Compare buying vs renting financial outcome', which is a specific verb and resource. It distinguishes itself from sibling tools that are other calculators (e.g., tax, EMI) by focusing on the unique decision of homeownership vs renting.

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?

It says 'Use when deciding between buying a home or renting', which explicitly states the context. No when-not or alternatives are given, but siblings are unrelated so exclusion is implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rehan1020/MCP-India-Stack'

If you have feedback or need assistance with the MCP directory API, please join our Discord server