Skip to main content
Glama

Netwise Paycheck Calculator

Calculate take-home pay

calculate_paycheck
Read-onlyIdempotent

Use this when the user asks 'how much is my paycheck after taxes', wants a paycheck calculator or take home pay calculator for a US job in 2026, or asks what a salary or hourly wage is after tax (e.g. '85k salary after taxes in California', 'what is 75000 a year biweekly after taxes', '$22 an hour 40 hours', 'how much tax comes out of my paycheck'). Computes federal income tax withholding with the IRS Pub. 15-T 2026 percentage method and Form W-4 inputs, Social Security, Medicare, Additional Medicare, state income tax and state payroll taxes (e.g. CA SDI, NJ FLI, WA Cares), pre-tax 401(k)/HSA/health premiums, net pay per check and per year, and effective rates. Returns a PDF estimate and a CSV with one row per 2026 paycheck. Does not run payroll, file tax returns, or produce pay stubs. Do not use to make a pay stub or proof of income.

Input Schema

NameRequiredDescriptionDefault
labelNoShort name for this scenario, e.g. 'Austin offer' or '401k at 10%'.
stateNoUS state where you work and live, as a code or name, e.g. CA, Texas, New Jersey, NYC. Omit for federal only.
localityNoOptional local tax area where the state supports it, e.g. nyc, yonkers, philadelphia, or a Maryland or Indiana county such as montgomery or marion.
hourly_rateNoHourly wage in USD, e.g. 22 for $22 an hour. Combine with hours_per_week.
k401_percentNoTraditional (pre-tax) 401(k) or 403(b) contribution as a percent of gross pay, e.g. 6 for 6%.
annual_salaryNoYearly salary before taxes in USD, e.g. 85000. Give this, or hourly_rate, or gross_per_paycheck.
filing_statusNoForm W-4 Step 1(c) filing status: single (or married filing separately, default), married (filing jointly), head_of_household.
pay_frequencyNoHow often you are paid: weekly (52), biweekly (26, every two weeks, default), semimonthly (24, twice a month), monthly (12).
hours_per_weekNoRegular hours worked per week for hourly pay, e.g. 40. Defaults to 40.
w4_step3_amountNoTotal dollar amount on W-4 Step 3 (dependents and other credits), e.g. 4400.
hsa_per_paycheckNoHSA contribution through payroll per paycheck in USD, e.g. 75.
other_dependentsNoOther dependents for W-4 Step 3 ($500 each), e.g. 1.
state_allowancesNoAllowances or exemptions claimed on the state withholding form (state W-4), e.g. 1. Defaults depend on the state.
w4_step2_checkedNoTrue if the Form W-4 Step 2 box is checked (two jobs, or married and the spouse also works). Default false.
children_under_17NoQualifying children under 17 for W-4 Step 3 ($2,200 each in 2026), e.g. 2. Ignored if w4_step3_amount is given.
k401_per_paycheckNoTraditional 401(k) contribution in dollars per paycheck, e.g. 200. Use instead of k401_percent.
roth_401k_percentNoRoth 401(k) (after-tax) contribution as a percent of gross pay, e.g. 4.
gross_per_paycheckNoGross pay per paycheck in USD before any deductions, e.g. 3200. Use instead of a salary or hourly rate.
overtime_multiplierNoOvertime pay multiplier, e.g. 1.5 for time-and-a-half (default) or 2 for double time.
state_filing_statusNoState withholding form status when it differs from the federal one, e.g. NJ 'B', CT 'A', AZ '2.0' (percent). Usually omit.
w4_step4b_deductionsNoW-4 Step 4(b) deductions per year, e.g. 5000.
w4_step4a_other_incomeNoW-4 Step 4(a) other income per year (not from jobs), e.g. 2000.
overtime_hours_per_weekNoOvertime hours per week paid at overtime_multiplier, e.g. 5. Defaults to 0.
claim_overtime_deductionNoTrue to add the 2026 qualified overtime deduction (the 'half' of time-and-a-half, up to $12,500 or $25,000 married) to W-4 Step 4(b), as the 2026 W-4 worksheet allows. Needs hourly_rate and overtime hours.
w4_step4c_extra_withholdingNoW-4 Step 4(c) extra federal withholding per paycheck, e.g. 50.
ytd_gross_before_this_checkNoGross pay already received from this job earlier in 2026, e.g. 150000. Only matters near the Social Security wage base or the $200,000 Additional Medicare threshold.
state_additional_withholdingNoExtra state withholding per paycheck in USD, e.g. 20.
health_insurance_per_paycheckNoPre-tax (section 125) health, dental and vision premiums and FSA per paycheck in USD, e.g. 120.

Output Schema

NameRequiredDescriptionDefault
labelYes
linesYes
notesYes
stateYes
downloadsYes
net_per_yearYes
state_methodYes
net_per_checkYes
pay_frequencyYes
gross_per_yearYes
taxes_per_yearYes
checks_per_yearYes
federal_bracketYes
gross_per_checkYes
state_supportedYes
taxes_per_checkYes
effective_tax_rateYes
effective_state_rateYes
effective_federal_rateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds substantive behavioral context: the exact tax methodology, pre-tax deductions handled, output artifacts (PDF estimate and CSV with one row per paycheck), and explicit non-goals such as not running payroll or filing tax returns.

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?

The description is front-loaded with usage triggers and then covers computations, outputs, and exclusions. It is appropriately sized for a complex 28-parameter tax calculator, though the first sentence is a long run-on with repetitive example phrasing.

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?

Given the full input schema, existing output schema, and safety annotations, the description is complete enough for an agent to understand when to call it, what it computes, what it returns, and what it does not do. No critical operational detail 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 28 parameters are already documented with examples and constraints. The description adds useful query examples that map to salary, state, and hourly inputs, but does not provide parameter semantics beyond what the schema already supplies.

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 specific verb and resource: computing take-home pay from salary, hourly wage, or gross pay, including federal/state withholding and deductions. It clearly distinguishes the tool from payroll processing and pay-stub generation, but it does not explicitly distinguish it from sibling tools like calculate_gross_up or compare_paychecks.

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?

It provides explicit triggering user questions such as 'how much is my paycheck after taxes' and '85k salary after taxes in California,' along with exclusions like not for pay stubs or proof of income. It lacks explicit routing to sibling alternatives, so it falls short of a full 5.

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