Skip to main content
Glama

Income tax: old vs new regime

compare_income_tax_regimes
Read-onlyIdempotent

Income tax for FY 2026-27 (tax year 2026-27) under the new and old regimes for a salaried resident individual below 60, including the standard deduction, rebate, marginal relief, surcharge and 4% cess. Starts from salary: the HRA exemption is worked out from basic pay, HRA received and rent. Old-regime deductions (HRA, 80C, 80D, own NPS 80CCD(1B), home loan interest) are optional inputs; employer NPS counts in both regimes (up to 14% of basic in the new regime, 10% in the old). Taxable income and total tax are rounded to the nearest Rs 10 (Income-tax Act, 2025, s.516).

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": {
      "gross_annual_income": "<gross_annual_income>"
    },
    "name": "compare_income_tax_regimes"
  }
}

Input Schema

NameRequiredDescriptionDefault
employer_npsNoEmployer NPS contribution for the year in rupees (both regimes, default 0)
rent_monthlyNoRent paid a month in rupees (default 0)
basic_monthlyNoBasic + DA a month in rupees (default: half of gross / 12). Used for HRA and the employer NPS limit
deduction_80cNoSection 80C investments in rupees, including employee EPF (old regime only, default 0)
deduction_80dNoSection 80D health insurance premium in rupees (old regime only, default 0)
own_nps_80ccd1bNoOwn NPS contribution under 80CCD(1B), in rupees (old regime only, default 0)
home_loan_interestNoInterest on a self-occupied home loan for the year in rupees (old regime only, default 0)
gross_annual_incomeYesGross salary for the year in rupees, including HRA, bonus and employer NPS
hra_received_monthlyNoHRA received a month in rupees (default 0)
lives_in_50_percent_cityNoLives in Mumbai, Delhi, Kolkata, Chennai, Bengaluru, Hyderabad, Pune or Ahmedabad (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / basic_monthly
      Added value: +{
      +  "description": "Basic + DA a month in rupees (default: half of gross / 12). Used for HRA and the employer NPS limit",
      +  "maximum": 5000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / deduction_80c / description
      Previous value: -"Section 80C investments in rupees (old regime only, default 0)"New value: +"Section 80C investments in rupees, including employee EPF (old regime only, default 0)"
    • changedInput schema / properties / deduction_80d / maximum
      Previous value: -50000New value: +100000
    • addedInput schema / properties / employer_nps
      Added value: +{
      +  "description": "Employer NPS contribution for the year in rupees (both regimes, default 0)",
      +  "maximum": 5000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / gross_annual_income / description
      Previous value: -"Gross salary for the year in rupees"New value: +"Gross salary for the year in rupees, including HRA, bonus and employer NPS"
    • addedInput schema / properties / home_loan_interest
      Added value: +{
      +  "description": "Interest on a self-occupied home loan for the year in rupees (old regime only, default 0)",
      +  "maximum": 200000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • removedInput schema / properties / hra_exemption
      Removed value: -{
      -  "description": "Exempt HRA in rupees (old regime only, default 0)",
      -  "maximum": 1000000,
      -  "minimum": 0,
      -  "type": "number"
      -}
    • addedInput schema / properties / hra_received_monthly
      Added value: +{
      +  "description": "HRA received a month in rupees (default 0)",
      +  "maximum": 2500000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / lives_in_50_percent_city
      Added value: +{
      +  "description": "Lives in Mumbai, Delhi, Kolkata, Chennai, Bengaluru, Hyderabad, Pune or Ahmedabad (default true)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / own_nps_80ccd1b
      Added value: +{
      +  "description": "Own NPS contribution under 80CCD(1B), in rupees (old regime only, default 0)",
      +  "maximum": 50000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / rent_monthly
      Added value: +{
      +  "description": "Rent paid a month in rupees (default 0)",
      +  "maximum": 2500000,
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive calculator, so the safety profile is covered. The description adds genuine behavioral context beyond that: the HRA exemption derivation from basic pay/HRA received/rent, the 14% vs 10% employer NPS caps per regime, and the Rs 10 rounding rule under s.516. It does not say what the returned comparison looks like or whether defaults silently substitute values, which is the remaining gap.

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 period, regimes and taxpayer profile, then the mechanics, then the rounding caveat — a logical order with no filler sentences. It is dense to the point of being a single run-on block, which slightly hurts scannability, but every clause carries factual content.

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 domain calculator with no output schema, the description covers scope, assumptions, defaults, legal basis and rounding well. What it omits is the shape of the result — whether it returns side-by-side tax under both regimes, the savings delta, or a component breakdown — which the agent cannot infer from structured fields.

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% and each of the 10 parameters carries its own units, ranges and default, so the baseline is 3. The description adds a synthesized cross-parameter rule (which deductions apply only in the old regime vs both, and that employer NPS is capped at 14%/10% of basic) that is more than a restatement, but it does not clarify the fallback behaviour of basic_monthly or the 50%-city boolean beyond what the schema states.

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 concrete computation and scope: income tax for FY 2026-27 under both the new and old regimes for a salaried resident individual below 60, with the specific components included (standard deduction, rebate, marginal relief, surcharge, cess). It does not, however, differentiate itself from siblings that overlap its HRA logic (e.g. hra_calculator) or from tds_calculator, so the agent must infer the boundary from the tax-regime framing alone.

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?

Scope conditions act as when-to-use guidance: salaried, resident, below 60, FY 2026-27, and it explicitly marks the old-regime deduction inputs as optional while noting employer NPS applies in both regimes. It stops short of naming an alternative tool or stating what to do for non-salaried/60+ cases, so there is no explicit exclusion path.

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