TeamPredict HR Calculators

US paycheck take-home pay

us_paycheck_take_home

Read-onlyIdempotent

Calculate US take-home (net) pay from a salary or an hourly wage for 2026, after federal income tax (from the Form W-4), Social Security, Medicare and the state's own income tax and payroll contributions, in any of the 50 states or DC. Use it for 'how much will I take home on $X in ?', for comparing states, or to price an offer; it also returns the full-year totals and what the employer pays on top. Use us_bonus_tax instead for tax withheld from a bonus, overtime_pay for the extra pay for overtime hours before tax, and hourly_to_salary for converting pay between hour, week, month and year without tax. Assumes the 2026 federal withholding method and the state's published employer withholding formula, one job, and a W-4 filed in the standard way.

Input Schema

Name	Required	Description	Default
`state`	Yes	Two-letter postal code of the state where the employee works and lives: all 50 states and DC (for example CA, NY, TX, DC).
`pay_type`	No	Whether the employee is paid a yearly salary or an hourly wage. Default salary.	salary
`local_tax`	No	Id of a city or county income tax to include (for example 'nyc' or 'yonkers' for New York). Leave out for none; an unknown id returns the ids that state accepts.
`filing_status`	No	Filing status on the federal Form W-4, step 1(c): single (or married filing separately), married (filing jointly) or head (head of household). Default single.	single
`pay_frequency`	No	How often the employee is paid: weekly (52 paychecks a year), biweekly (26), semimonthly (24, twice a month) or monthly (12). Default biweekly.	biweekly
`hourly_rate_usd`	No	Hourly wage in US dollars. Required when pay_type is hourly. For example 25.
`state_allowances`	No	Allowances or exemptions on the state's own withholding form, for states that have one. Leave out to use the typical single worker's number for that state.
`annual_salary_usd`	No	Yearly gross salary in US dollars. Required when pay_type is salary. For example 60000.
`w4_step2_checkbox`	No	The 'multiple jobs or spouse works' box in Form W-4 step 2(c). Default false.
`w4_other_dependents`	No	Other dependents for Form W-4 step 3 (a $500 credit each). Default 0.
`hsa_usd_per_paycheck`	No	Pre-tax HSA contribution through payroll per paycheck, in US dollars (capped at the 2026 family limit). Default 0.
`w4_children_under_17`	No	Qualifying children under 17 for Form W-4 step 3 (a $2,200 credit each in 2026). Default 0.
`regular_hours_per_week`	No	Regular (straight-time) hours per week, hourly pay only. Default 40.
`overtime_hours_per_week`	No	Overtime hours per week paid at time and a half, hourly pay only. Default 0.
`traditional_401k_percent`	No	Pre-tax 401(k) contribution as a percentage of gross pay, 0 to 100 (capped at the 2026 IRS limit). Default 0.
`w4_deductions_usd_per_year`	No	Deductions above the standard deduction, Form W-4 step 4(b), in US dollars per year. Default 0.
`w4_other_income_usd_per_year`	No	Other income not from jobs, Form W-4 step 4(a), in US dollars per year. Default 0.
`health_premiums_usd_per_paycheck`	No	Pre-tax health, dental and vision premiums per paycheck, in US dollars. Default 0.
`w4_extra_withholding_usd_per_paycheck`	No	Extra federal withholding per paycheck, Form W-4 step 4(c), in US dollars. Default 0.

Output Schema

Name	Required	Description
`inputs`	Yes	The inputs as used, with defaults filled in.
`results`	Yes	The computed numbers. Unavailable numbers are null.
`summary`	Yes	One or two plain sentences with the headline numbers.
`calculator_url`	Yes	The TeamPredict calculator page that shows the same calculation, where a person can change the inputs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered; the description adds real value by disclosing that it returns full-year totals and employer-side cost, and by enumerating the payroll contributions modeled (federal, FICA, state income tax, state payroll contributions). It does not discuss precision/rounding or edge-case behavior, keeping it short of a 5.

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 the verb and scope, then usage exemplars, then exclusions, then assumptions — a sensible order with no filler. The final assumption sentence is long and packs several constraints, but each carries information an agent needs.

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 19-parameter calculator with an output schema and full annotation coverage, the description covers purpose, honest usage boundaries, sibling disambiguation, and the modeling assumptions. Nothing needed to decide whether to call it and interpret the result 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 description coverage is 100%, so all 19 parameters are already documented in the schema, and the description names no individual parameter. It does add framing that ties the w4_* inputs to Form W-4 and mentions state payroll contributions, but it gives no syntax, ranges, or default guidance 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 verb and resource ('Calculate US take-home (net) pay') plus scope: 2026, salary or hourly, all 50 states or DC, and the exact taxes included. The sibling alternatives named later make the boundary between this and us_bonus_tax / overtime_pay / hourly_to_salary unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete selection contexts ('how much will I take home on $X in <state>?', comparing states, pricing an offer) and explicitly routes three sibling cases elsewhere: bonus withholding, pre-tax overtime pay, and pure pay-period conversion. Also states the modeling assumptions (one job, standard W-4, 2026 withholding method) that must hold for the result to be valid.

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

All TeamPredict HR Calculators 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?