Skip to main content
Glama
Sign In
statetakehome-mcp

statetakehome-mcp

by tresor4k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

US Take-Home Pay Calculator

us_take_home_pay

Compute net take-home pay for a US W-2 employee after federal, state, and FICA taxes, with optional pre-tax 401(k) and health deductions.

Instructions

Computes net take-home pay for a US W-2 employee: federal income tax, state income tax (all 50 states + DC), FICA (Social Security + Medicare + Additional Medicare), and state-specific extras (e.g. CA SDI, OR transit tax). Supports pre-tax 401(k) and health-insurance deductions and per-paycheck breakdowns. Example input: { "gross": 75000, "state": "CA", "filingStatus": "single" }. 2026 tax year — estimates, not tax advice; brackets from Tax Foundation (Jan 1, 2026) & IRS.

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": {
      "gross": "<gross>",
      "state": "<state>",
      "filingStatus": "<filingStatus>"
    },
    "name": "us_take_home_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesAnnual gross income in USD, e.g. 75000.
stateYesTwo-letter US state or DC postal code, e.g. "CA", "TX", "NY".
dependentsNoNumber of dependents claimed (informational; not currently used in the federal/state bracket math).
filingStatusYesIRS filing status.
payFrequencyNoPay frequency; the result always includes a full per-paycheck breakdown for all frequencies regardless of this value.
pretax401kPctNoPre-tax 401(k) contribution as a percent of gross pay (0-100), capped at the 2026 employee deferral limit ($23,500).
pretaxHealthAnnualNoAnnual pre-tax health insurance / HSA premiums in USD, excluded from both income tax and FICA wages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses coverage (federal, state, FICA, state-specific extras), pre-tax deductions, per-paycheck breakdown, example input, tax year, and a disclaimer about estimates. It does not mention if the tool is read-only, but as a calculator this is implicit.

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 a single paragraph with several sentences, no wasted words. It is front-loaded with the primary action. Some bullet-point structuring could improve scannability, but it remains concise.

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?

The description outlines what the tool computes and includes an example input, but without an output schema, it does not describe the return structure (e.g., named fields, per-paycheck items). For a calculator returning detailed breakdowns, this is a notable gap.

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 the baseline is 3. The description adds context by listing the tax components and mentioning pre-tax deductions, but the parameter descriptions in the schema are already detailed. The extra value is moderate.

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?

The description specifies a precise verb ('Computes net take-home pay') and resource ('US W-2 employee'), lists covered taxes and deductions, and inherently distinguishes from siblings (self-employment and capital gains taxes).

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?

The description clearly defines the tool's scope (W-2 employees, 2026 tax year) and lists what it includes, which implies when to use it. However, it does not explicitly contrast with sibling tools or state when not to use it.

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

Deploy Server

Other Tools