India Salary Calculator

Gross salary needed for a net amount in India

gross_for_target_net

Read-onlyIdempotent

The gross yearly salary in India that leaves a given take-home pay, with the same situation options as net_salary. Use it to set a salary ask or check an offer.

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": {
      "net_target": "<net_target>"
    },
    "name": "gross_for_target_net"
  }
}

Input Schema

Name	Required	Description
`age`	No	Age; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
`epf`	No	EPF contribution: none = Not in this calculation; ceiling = 12% on basic up to ₹15,000/month; full = 12% on full basic. Default none.
`hra`	No	HRA received (₹ / year). Default 0.
`nps`	No	Own NPS, 80CCD(1B) (₹ / year). Default 0.
`rent`	No	Rent paid (₹ / year). Default 0.
`metro`	No	Metro city (Delhi, Mumbai, Kolkata, Chennai) Default false.
`period`	No	Whether net_target is per year or per month. Default year.
`regime`	No	Tax regime: new = New regime (default); old = Old regime; best = Whichever is lower. Default new.
`sec80c`	No	80C investments besides EPF. PPF, ELSS, life insurance, tuition fees, principal on a home loan. (₹ / year). Default 0.
`sec80d`	No	80D health insurance premium (₹ / year). Default 0.
`prof_tax`	No	Professional tax (₹2,500/year). Charged by states such as Maharashtra, Karnataka, West Bengal. Default false.
`basic_pct`	No	Basic salary. Basic pay as a share of gross; EPF, HRA and NPS limits work on it. (% of gross). Default 50.
`home_loan`	No	Home loan interest, 24(b) (₹ / year). Default 0.
`fx_per_eur`	No	Exchange rate: 1 euro = this many INR, for the euro amounts. Default 90 (indicative).
`net_target`	Yes	Take-home pay wanted, in INR
`bonus_annual`	No	Yearly bonus in INR. Default 0.
`employer_nps`	No	Employer NPS. Deductible in both regimes: up to 14% of basic (new), 10% (old). (% of basic). Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that the situation options mirror net_salary, which is useful context, but says nothing about the shape of the result (single figure vs. breakdown) or edge cases such as an unreachable target.

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 tight sentences with the core computation front-loaded and the use case second. Nothing is redundant and no wording is wasted.

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 17-parameter calculation tool with no output schema, the description is thin: it does not describe the returned figure or any breakdown, and its 'gross yearly salary' phrasing sits awkwardly against the period parameter that allows monthly targets. The rich schema compensates for most parameter gaps, keeping this at minimum-viable.

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% across all 17 parameters, so the schema fully documents each option, including enums and defaults. The description contributes only the pointer that these options match net_salary, adding no meaning beyond the schema; 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?

States a specific inverse computation: the gross salary that produces a given take-home pay in India. Referencing net_salary implicitly distinguishes it as the reverse of that sibling, but the differentiation is left for the agent to infer rather than spelled out.

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?

One sentence of context is given ('set a salary ask or check an offer'), which is a genuine when-to-use cue. However, there is no guidance on when to prefer net_salary or compare_with_netherlands instead, and no note on what to do if no gross satisfies the target.

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

All India Salary Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?