Skip to main content
Glama

Tip & Overtime Deductions

Does my job qualify for no tax on tips? Treasury Tipped Occupation Code lookup

tipped_occupation_code
Read-onlyIdempotent

Finds the Treasury Tipped Occupation Code (W-2 box 14b) for a job title, from the IRS list of 71 occupations that customarily received tips before 2025, with the IRS description and examples, the related SOC code, and what the tips deduction is worth at that occupation's median pay (BLS OEWS May 2025): federal income tax saved per $1,000 of tips and the most it can save in a year. Use for 'does my job qualify for no tax on tips', 'what is my tipped occupation code', 'is a barista a tipped occupation'. Pass a job title, or a 3-digit code.

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": {
      "job": "<job>"
    },
    "name": "tipped_occupation_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesJob title in the user's words, or a 3-digit TTOC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile needs no restating. The description does add real behavioral value by enumerating output content (IRS description/examples, SOC code, BLS median-pay savings math) since no output schema exists. It omits what happens on a non-matching or ambiguous job title, which matters for a free-text lookup.

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?

Three sentences, each with a distinct job: what it returns, when to use it, and how to call it. The verb and resource are front-loaded and the dense clause about savings math is information the agent needs given there is no output schema.

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?

For a single-parameter, read-only lookup with no output schema, the description covers source, returned fields, and the pay-based computation, which is the bulk of what an agent needs. The remaining gap is failure/ambiguity behavior on unmatched titles.

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 coverage is 100% and the schema text ('Job title in the user's words, or a 3-digit TTOC') is essentially duplicated by 'Pass a job title, or a 3-digit code.' No additional format, partial-match, or disambiguation semantics are supplied beyond what the schema already states.

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 states a specific verb ('Finds') and a precise resource ('Treasury Tipped Occupation Code (W-2 box 14b)'), and even anchors the source corpus (IRS list of 71 occupations). It implicitly separates itself from w2_tip_overtime_boxes by naming box 14b, but never explicitly contrasts with either sibling, so it falls 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Three concrete example user phrasings ('does my job qualify for no tax on tips', 'is a barista a tipped occupation') give a clear picture of when this tool applies, and the last sentence says what to pass. There is no when-not guidance or routing to tip_overtime_deduction / w2_tip_overtime_boxes for adjacent questions.

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.