Skip to main content
Glama

United States Salary and Income Tax Calculator

Employer cost of a salary in United States

employer_cost
Read-onlyIdempotent

What a salary in United States costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "employer_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
hsaNoHSA contribution. Health Savings Account, 2026 limit $4,400 self-only, $8,750 family. Free of income tax and FICA through payroll. ($ / year). Default 0.
stateNoState: 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.11M); 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.
filingNoFiling status (unmarried). Married people file jointly here; switch on "Married" above.: single = Single; hoh = Head of household (with a qualifying child). Default single.
pretaxNoOther pre-tax deductions. Employee share of health premiums, FSA, commuter benefits (section 125): free of income tax and FICA. ($ / year). Default 0.
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
tax_yearNoTax year. Offered: 2026 (final), 2025 (final), 2024 (final). Default 2026. A year that is not listed is not available for this country.
fx_per_eurNoExchange rate: 1 euro = this many USD, for the euro amounts. Default 1.08 (indicative).
pension_pctNoVoluntary employee pension contribution through payroll, % of salary. Default 0.
bonus_annualNoYearly bonus in USD. Default 0.
gross_annualNoGross yearly salary in USD
budget_annualNoTotal yearly employer budget in USD, to find the gross salary it allows
spouse_incomeNoPartner's gross yearly income in USD, for joint taxation and spouse allowances. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / state / description
      Previous value: -"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."New value: +"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.11M); 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."
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year. Offered: 2026 (final), 2025 (final), 2024 (final). Default 2026. A year that is not listed is not available for this country.",
      +  "enum": [
      +    2026,
      +    2025,
      +    2024
      +  ],
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and the description's bar is lower. The description adds that employer social contributions are itemised in the result and that the tool is bidirectional, which is genuine behavioral context. It does not mention jurisdiction limits, year availability beyond the enum, or what happens when neither gross_annual nor budget_annual is supplied.

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 sentences, no filler, and the core function is front-loaded before the reverse-direction qualifier. Every clause carries information; nothing repeats the name or title.

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 14-parameter payroll/tax tool with no output schema, the description covers the input contract but says nothing about the shape of the itemised result or about assumptions such as which contributions are included. Given the rich schema, this is adequate but leaves the caller guessing at output structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds a cross-parameter contract the schema cannot express: gross_annual drives forward calculation while budget_annual drives the reverse solve, and one should be given. That directional meaning is not inferable from two optional number fields alone.

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 computation on a specific resource: employer cost of a US salary, including itemised employer social contributions, plus the inverse direction (budget to gross). An agent can tell the two modes apart from the text. It does not, however, contrast itself against siblings such as net_salary or gross_for_target_net, so it stops short of a 5.

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?

The final sentence 'Give gross_annual or budget_annual' gives explicit guidance on which input selects which computation direction, which is real usage instruction. There is no guidance on when to choose this tool over net_salary or gross_for_target_net, and no stated prerequisites or restrictions on the inputs.

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