Skip to main content
Glama

New York State Workers' Compensation Hub

NY average weekly wage with tips, board and concurrent wages

calculate_aww_with_adjustments
Read-onlyIdempotent

The average weekly wage the way the Pro Workspace's global AWW works it out: earnings_method "steady" (earnings ÷ days worked × the 200/260/300/365 multiplier for a 4-/5-/6-/7-day week ÷ 52) or "irregular" (earnings ÷ weeks worked), plus weekly tips, the weekly value of board, and a concurrent employer's weekly wage. With a date of accident it adds the two-thirds weekly rate within the max and min. For a 1–3 day week use calculate_aww. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice.

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": {
      "earnings_method": "<earnings_method>",
      "total_earnings": "<total_earnings>"
    },
    "name": "calculate_aww_with_adjustments"
  }
}

Input Schema

NameRequiredDescriptionDefault
days_workedNosteady: days actually worked in the period.
weekly_tipsNoOptional: weekly tips, in dollars.
weekly_boardNoOptional: weekly value of board/lodging, in dollars.
weeks_workedNoirregular: weeks actually worked.
days_per_weekNosteady: days normally worked each week.
total_earningsYesGross earnings in the period, in dollars.
earnings_methodYes
date_of_accidentNoOptional: adds the weekly rate. YYYY-MM-DD.
concurrent_weekly_wageNoOptional: weekly wage from a concurrent employer, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the calc-core engine never estimates, a missing input yields status "missing" with nothing calculated, and the response includes steps plus a not-legal-advice notice. That is solid added context, though it stops short of detailing output structure or error behavior for invalid combinations (e.g., method/days mismatches).

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?

Dense but front-loaded, leading with the core computation and deferring the sibling redirect and return details. A few formula fragments are packed into one long sentence, which slightly hurts scanability, but nearly every clause carries information an 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?

For a 9-parameter calculation tool with no output schema, the description covers method selection, input dependencies, missing-input behavior, and the shape of the return (figures, steps with rule and engine function, disclaimer). Nothing material needed to call it correctly appears to be absent.

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 89%, so the baseline is already high, yet the description still adds meaning the schema lacks: the steady formula's 200/260/300/365 multipliers, the ÷52 step, the irregular earnings ÷ weeks worked rule, and the fact that date_of_accident triggers the two-thirds weekly rate within max and min. The optional tips, board and concurrent wage inputs are named and characterized as weekly additions.

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?

States a specific computation (NY average weekly wage including tips, board and concurrent wages) and names the two earnings methods it implements. It also explicitly distinguishes itself from the sibling calculate_aww by limiting that one to 1–3 day weeks, so an agent can route correctly without opening a schema.

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?

Gives clear usage context: New York State only, steady vs irregular method selection, and an explicit redirect to calculate_aww for 1–3 day weeks. It does not cover when to prefer calculate_weekly_rate or get_max_min_rate for the rate portion, so the alternatives coverage is partial rather than exhaustive.

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.