Skip to main content
Glama

India Salary Calculator

Net salary in India (2026)

net_salary
Read-onlyIdempotent

Take-home pay for an employee in India from a gross yearly salary in INR, with 2026 rules: every tax and contribution itemised with its local name, the effective and marginal rate, employer cost and the step-by-step workings. Covers: New and old regime side by side, or the better of the two; 87A rebate with marginal relief, surcharge with marginal relief, 4% cess; Old regime: HRA, 80C, 80D, 80CCD(1B), home loan interest, senior slabs; EPF (statutory ceiling or full basic), employer NPS, professional tax.

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": "<gross_annual>"
    },
    "name": "net_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
epfNoEPF contribution: none = Not in this calculation; ceiling = 12% on basic up to ₹15,000/month; full = 12% on full basic. Default none.
hraNoHRA received (₹ / year). Default 0.
npsNoOwn NPS, 80CCD(1B) (₹ / year). Default 0.
rentNoRent paid (₹ / year). Default 0.
metroNoMetro city (Delhi, Mumbai, Kolkata, Chennai) Default false.
regimeNoTax regime: new = New regime (default); old = Old regime; best = Whichever is lower. Default new.
sec80cNo80C investments besides EPF. PPF, ELSS, life insurance, tuition fees, principal on a home loan. (₹ / year). Default 0.
sec80dNo80D health insurance premium (₹ / year). Default 0.
prof_taxNoProfessional tax (₹2,500/year). Charged by states such as Maharashtra, Karnataka, West Bengal. Default false.
basic_pctNoBasic salary. Basic pay as a share of gross; EPF, HRA and NPS limits work on it. (% of gross). Default 50.
home_loanNoHome loan interest, 24(b) (₹ / year). Default 0.
fx_per_eurNoExchange rate: 1 euro = this many INR, for the euro amounts. Default 90 (indicative).
bonus_annualNoYearly bonus in INR. Default 0.
employer_npsNoEmployer NPS. Deductible in both regimes: up to 14% of basic (new), 10% (old). (% of basic). Default 0.
gross_annualYesGross yearly salary in INR, without bonus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's contribution is about output shape. It does that well: itemised taxes with local names, effective and marginal rates, employer cost, and step-by-step workings, which is valuable given there is no output schema. Minor gap – nothing on output format or precision/rounding.

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?

Purpose is front-loaded in the first clause before the 'Covers:' inventory. The single dense paragraph has no filler, though the coverage list is long enough that it reads as a feature dump rather than agent-facing guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter calculator with no output schema, the description supplies both the scope of computation and the shape of the return values, while the schema fully documents inputs. Nothing an agent needs in order to call this correctly 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 baseline is 3 and the schema already explains every one of the 16 parameters including their defaults, enums and units. The description adds some framing for the regime ('New and old regime side by side, or the better of the two') and EPF ('statutory ceiling or full basic') options, but stays at the level the schema already sets.

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?

Opens with a specific verb+resource: take-home pay for an Indian employee computed from a gross yearly salary in INR under 2026 rules. The scope (net salary from gross) is unambiguous. It stops short of naming alternatives, so it does not actively route the agent away from gross_for_target_net, the inverse calculation.

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?

Usage is only implied by 'from a gross yearly salary' – the agent must infer this is the forward gross-to-net direction. There is no explicit when-to-use, no exclusion, and no pointer to siblings such as gross_for_target_net, employer_cost, or income_tax_return, which overlap in subject matter.

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