United States Salary Calculator

Gross salary needed for a net amount in United States

gross_for_target_net

Read-onlyIdempotent

The gross yearly salary in United States 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.
`hsa`	No	HSA contribution. Health Savings Account, 2026 limit $4,400 self-only, $8,750 family. Free of income tax and FICA through payroll. ($ / year). Default 0.
`state`	No	State: none = No state income tax (TX, FL, NV, TN, SD, WY, AK, NH); CA = California; NY = New York (outside NYC); NYC = New York City; IL = Illinois (4.95% flat); MA = Massachusetts (5%, 9% above $1.08M); PA = Pennsylvania (3.07% flat); NJ = New Jersey; CO = Colorado (4.4% flat); NC = North Carolina (3.99% flat); GA = Georgia (4.99% flat); AZ = Arizona (2.5% flat); WA = Washington (no income tax, WA Cares + PFML). Default none.
`filing`	No	Filing status (unmarried). Married people file jointly here; switch on "Married" above.: single = Single; hoh = Head of household (with a qualifying child). Default single.
`period`	No	Whether net_target is per year or per month. Default year.
`pretax`	No	Other pre-tax deductions. Employee share of health premiums, FSA, commuter benefits (section 125): free of income tax and FICA. ($ / year). Default 0.
`married`	No	Married or registered partner. Default false.
`children`	No	Number of dependent children. Default 0.
`fx_per_eur`	No	Exchange rate: 1 euro = this many USD, for the euro amounts. Default 1.08 (indicative).
`net_target`	Yes	Take-home pay wanted, in USD
`pension_pct`	No	Voluntary employee pension contribution through payroll, % of salary. Default 0.
`bonus_annual`	No	Yearly bonus in USD. Default 0.
`spouse_income`	No	Partner's gross yearly income in USD, for joint taxation and spouse allowances. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the US scope and inverse-calculation context but does not disclose tax-rate assumptions, accuracy limits, or return-value detail.

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 tightly written sentences with the result and scope front-loaded. Every phrase earns its place and there is no redundant restatement of the title.

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?

Covers the core purpose, US scope, yearly basis, required net target, and use cases despite the tool having 13 parameters. The pointer to net_salary helps with option semantics, though it stops short of describing assumptions or return shape, which is acceptable given no output schema.

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 the 13 parameters are fully documented in the schema, so baseline is 3. The description only says the tool uses the same situation options as net_salary, adding no parameter-level meaning beyond the schema.

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?

States a specific calculation: the gross yearly salary in the United States that leaves a given take-home pay. It distinguishes itself from sibling net_salary by describing the inverse relationship and referencing the same situation options.

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?

Gives clear use cases: setting a salary ask or checking an offer, and points to net_salary for situation options. It lacks explicit when-not guidance or routing to the other calculation siblings such as employer_cost or compare_with_netherlands.

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

All United States 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?