Skip to main content
Glama

Estimate My Paycheck

Calculate take-home pay

calculate_paycheck
Read-onlyIdempotent

Compute a US paycheck for 2026: gross, each tax and pre-tax deduction, and take-home pay per paycheck and per year, for a salary or an hourly rate (overtime over 40 hours at 1.5 times) in any state or DC. Federal withholding follows the annual tax on wages; local city and county taxes are not included (the answer names them when material).

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": {
      "state": "<state>"
    },
    "name": "calculate_paycheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code or name: TX, CA, new-york, DC.
salaryNoAnnual gross salary in dollars. Give this or hourly_rate.
tax_yearNoTax year, 2026 or 2027. Default: the year in force today (2026 now; 2027 from January 1, 2027).
residencyNoresident (default), nonresident (e.g. H-1B first year: taxed as single), student (F/J/M/Q nonresident: no FICA).
hourly_rateNoHourly rate in dollars, instead of salary.
k401_percentNoPre-tax 401(k) contribution, percent of gross. Default 0.
filing_statusNoDefault single.
pay_frequencyNoDefault biweekly.
hours_per_weekNoHours a week with hourly_rate (over 40 paid at 1.5 times). Default 40.
health_per_paycheckNoPre-tax health premium per paycheck, dollars. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year, 2026 or 2027. Default: the year in force today (2026 now; 2027 from January 1, 2027).",
      +  "example": 2026,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-open-world, and the description is consistent with that. Beyond annotations it discloses the federal withholding method (annual tax on wages), the overtime rule (over 40 hours at 1.5x), and that local city/county taxes are excluded but named when material — real behavioral context an agent would otherwise have to guess. It does not say how precise or approximate the output is, which keeps it from 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?

Two tight sentences led by the core action and output list, with the tax-scope caveat trailing where it belongs. Nearly every clause carries information. The parenthetical about local taxes is slightly awkward but earns its place.

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?

With no output schema, the description does the work of telling the agent what comes back: gross, itemized taxes and deductions, and per-paycheck and annual take-home. It also flags the main accuracy boundary (no local taxes). For a 10-parameter calculation tool this is close to complete, missing only a note on assumptions or rounding.

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 is 3, yet the description still adds meaning: it frames salary vs hourly_rate as an either/or, clarifies that overtime hours are paid at 1.5x (relevant to hours_per_week), and confirms state coverage extends to DC. It doesn't touch residency or filing_status effects, which the schema already handles.

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 precise verb and resource: compute a US paycheck for 2026, returning gross, each tax and pre-tax deduction, and take-home pay per paycheck and per year. The supported inputs (salary or hourly with 1.5x overtime, any state or DC) make the scope unmistakable. It stops short of explicitly naming how it differs from calculate_bonus_tax or compare_states, so it lands at 4 rather than 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?

Usage is implied by the scope statement: use this when a full take-home calculation is needed for a given state and either a salary or an hourly rate. The limitation on local city/county taxes is a useful scoping caveat. No sibling alternative is named and there is no explicit when-not-to-use guidance.

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