Skip to main content
Glama

Tip & Overtime Deductions

How much of my tips and overtime can I deduct (no tax on tips / no tax on overtime)

tip_overtime_deduction
Read-onlyIdempotent

Works out the federal 'no tax on tips' and 'no tax on overtime' deductions (Schedule 1-A, Form 1040, tax years 2025-2028) from what the person has: W-2 box 12 code TP and TT and box 14b, Form 4137, 1099s, or pay stubs before the W-2 arrives (hours over 40 and hourly rate, or overtime pay and its multiplier). Returns each deduction with the math line by line as it goes on Schedule 1-A, the Form 1040 line it lands on, the estimated federal income tax saved, what is still unknown, a citation for every rule, and a worksheet link that opens the filled-in Schedule 1-A worksheet to print or hand to a preparer. Use for 'how much of my tips can I deduct', 'does no tax on overtime apply to me', 'what goes on Schedule 1-A', 'I made $X in tips as a server'. Only the FLSA half of time-and-a-half counts as qualified overtime. Married filing separately gets nothing. Pass dollar amounts as numbers. Filing status and income (AGI) set the phase-out and the tax-saved estimate; without them the result says what is missing instead of assuming them.

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": "tip_overtime_deduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
agiNoAdjusted gross income (Form 1040 line 11b), dollars. Used as MAGI unless magi is given.
jobsNoOne entry per employer (W-2).
magiNoModified AGI if different: AGI plus excluded Puerto Rico / foreign earned income (Schedule 1-A line 3)
ot_1099NoQualified overtime on Form 1099-NEC box 1d / 1099-MISC box 14
tax_yearNoTax year (default 2026, filed in 2027)
valid_ssnNofalse if the person (or the spouse who earned the tips/overtime) has no Social Security number valid for work. Default true.
filing_statusNosingle, mfj (married filing jointly), mfs (married filing separately), hoh (head of household), qss (qualifying surviving spouse)
self_employedNoTips earned in the person's own business (1099s).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, but the description goes well past that: it enumerates what is returned (line-by-line Schedule 1-A math, the Form 1040 line, estimated federal tax saved, unknowns, a citation per rule, a filled worksheet link) and states substantive eligibility rules (MFS disqualified, FLSA-exempt overtime yields nothing). It also flags that filing status and AGI drive the phase-out, so the agent knows those inputs change the answer rather than just the formatting.

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?

It is front-loaded with the core purpose and the payoff (deduction + math + citation) before the example queries. It is a single very long run-on paragraph, and some return-format detail (the worksheet link for printing or handing to a preparer) could be tightened. Dense but nearly every clause carries information the 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?

There is no output schema, and the description compensates by describing the return payload in detail, including the 'what is still unknown' element that prevents the agent from inventing missing inputs. All 8 parameters are schema-documented at 100% coverage, so the description only needs to add the cross-parameter logic (phase-out driven by filing status and AGI) and it does. Nothing an agent needs to call this tool correctly appears to be missing.

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 with the schema doing the work. The description still adds meaning beyond the schema: it explains that AGI and filing status set the phase-out and the tax-saved estimate, that dollar amounts should be passed as numbers, and that pay-stub alternatives are accepted before a W-2 exists. That is real interpretive value, though it doesn't walk through individual field names.

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 opens with a specific verb+resource: it 'works out the federal no tax on tips and no tax on overtime deductions,' and anchors that to Schedule 1-A, Form 1040, and tax years 2025-2028. That is far more concrete than a restated title. It stops short of naming or contrasting the sibling tools (w2_tip_overtime_boxes, tipped_occupation_code), so the agent must infer that this one computes the deduction rather than parses a box or looks up an occupation code.

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?

Concrete use-triggers are supplied verbatim ('how much of my tips can I deduct', 'does no tax on overtime apply to me', 'what goes on Schedule 1-A', 'I made $X in tips as a server'), plus exclusions: only the FLSA half of time-and-a-half qualifies, and married-filing-separately gets nothing. Missing-input behavior is also stated ('the result says what is missing instead of assuming them'), which tells the agent it can call with partial data. No alternative tool is named for cases that belong elsewhere, so it falls short of a 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.