Skip to main content
Glama

HRA Calculator

hra_calculator
Read-onlyIdempotent

How much of your house rent allowance is tax-free. Same calculation as https://paisafinder.com/calculators/hra-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": "hra_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
hraNoHRA received (monthly) (rupees)
rentNoRent paid (monthly) (rupees)
basicNoBasic salary (monthly) (rupees)
metroNoDo you live in a 50% city?: 1 = Yes, 0 = No. Yes for Mumbai, Delhi, Kolkata, Chennai, Bengaluru, Hyderabad, Pune, Ahmedabad (from April 2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / metro / description
      Previous value: -"50% city? (1=Yes 0=No). Yes for Mumbai, Delhi, Kolkata, Chennai, Bengaluru, Hyderabad, Pune, Ahmedabad (from April 2026)"New value: +"Do you live in a 50% city?: 1 = Yes, 0 = No. Yes for Mumbai, Delhi, Kolkata, Chennai, Bengaluru, Hyderabad, Pune, Ahmedabad (from April 2026)"
    • addedInput schema / properties / metro / enum
      Added value: +[
      +  1,
      +  0
      +]
    • removedInput schema / properties / metro / maximum
      Removed value: -1
    • removedInput schema / properties / metro / minimum
      Removed value: -0
  2. Changed1 schema field changed
    • changedInput schema / properties / metro / description
      Previous value: -"Metro city? (1=Yes 0=No). Delhi, Mumbai, Kolkata, Chennai = metro"New value: +"50% city? (1=Yes 0=No). Yes for Mumbai, Delhi, Kolkata, Chennai, Bengaluru, Hyderabad, Pune, Ahmedabad (from April 2026)"
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that omitted inputs fall back to schema defaults and points to an external reference implementation, but it does not disclose the shape of the result (monthly vs annual exemption), which matters for a tool with no output schema.

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?

Two short sentences, front-loaded with the outcome, followed by a verifiability reference and the defaults note. Nothing is padded, though the external URL is more provenance than operational guidance.

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 four-parameter, zero-required, closed-world calculator whose schema is fully described, the definition covers purpose and default handling adequately. The main residual gap is that it never says whether the returned exemption is monthly or annual, which an agent may need when reporting results.

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 the four parameters, including the metro enum and its city list, are already fully documented with defaults and bounds. The description only restates the default behavior, adding no new meaning beyond the schema — the baseline 3 applies.

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 computed outcome for a specific resource: the tax-free portion of house rent allowance. That is enough to separate it from siblings like calculate_salary_in_hand or compare_income_tax_regimes, though it never names an alternative explicitly.

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?

It gives one useful usage fact — every input is optional and defaults apply — but says nothing about when to reach for this versus rent_vs_buy_calculator or calculate_salary_in_hand, and gives no exclusions or prerequisites.

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