Skip to main content
Glama

Tip & Overtime Deductions

W-2 box 12 TP, TT and box 14b for each employee, from payroll rows

w2_tip_overtime_boxes
Read-onlyIdempotent

For an owner, bookkeeper or payroll person: works out the new 2026 Form W-2 figures for each employee from payroll rows: box 12 code TP (cash tips reported to the employer), box 12 code TT (qualified overtime: hours over 40 in each FLSA workweek x 0.5 x the regular rate, where the regular rate includes non-discretionary bonuses, tip credit and service charges paid out) and box 14b (Treasury Tipped Occupation Code, suggested from the role). Pass one row per employee per workweek, as rows or as a pasted CSV/tab table with a header (employee, week_start, hours, rate, tips, role; optional tip_credit, other_pay, service_charges, ttoc, exempt). Returns per-employee boxes, every overtime week with its math, flags, and a link to a printable sheet. W-2s for 2026 are due January 31, 2027.

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

Input Schema

NameRequiredDescriptionDefault
rowsNo
tableNoPasted CSV or tab-separated table with a header row
tax_yearNoDefault 2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low, and the description clears it by disclosing the actual computation rule (hours over 40 x 0.5 x regular rate, with the regular rate including non-discretionary bonuses, tip credit and service charges) and what comes back (per-employee boxes, every overtime week with its math, flags, printable-sheet link). It stops short of stating behavior for edge cases such as missing rates or conflicting rows versus table input.

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?

Purpose is front-loaded in the first clause and the later sentences cover input shape, returns and deadline in a logical order. It is a single dense block with a deeply nested parenthetical formula, which makes it harder to scan than it needs to be, but little of the content is wasted.

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?

There is no output schema, so the description correctly spends words on the return value, and for a self-contained read-only calculation with no auth, cost or persistence concerns (employee initials are explicitly not stored) that is nearly enough. The remaining gap is that it does not say what happens if both rows and table are supplied, or which wins.

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?

With 67% schema coverage, the description compensates by walking through every field group (employee, week_start, hours, rate, tips, role; optional tip_credit, other_pay, service_charges, ttoc, exempt) and, crucially, explaining how tip_credit/other_pay/service_charges feed the regular rate — meaning the schema alone does not convey. It does not explain what exempt toggles or how a supplied ttoc overrides the role-derived suggestion.

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 names a precise verb-and-resource pairing — deriving 2026 Form W-2 box 12 code TP, box 12 code TT and box 14b figures per employee from payroll rows — and even states the computation for TT. An agent can tell this apart from a deduction calculator or a bare TTC lookup without opening any schema.

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?

It gives the audience ('owner, bookkeeper or payroll person') and the required invocation shape ('pass one row per employee per workweek, as rows or as a pasted CSV/tab table with a header'), which is real usage context. However, it never says when not to use it or which sibling (tip_overtime_deduction, tipped_occupation_code) to prefer when only part of the job is needed, so selection guidance is implied at best.

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.