Skip to main content
Glama

New York State Workers' Compensation Hub

NY schedule loss of use (SLU) award

calculate_slu_award
Read-onlyIdempotent

A schedule loss of use award for one or more scheduled members: weeks on the schedule × loss of use % × the weekly rate for the date of accident, plus any protracted healing period credit (weeks at temporary total beyond the longest healing period, §15(4-a)). With prior_payments (0 if none) it adds the money moving, the 15% attorney fee rounded down to $5 (the OC-400.1 amount) and the net. With an employer reimbursement it splits the money and the fees between claimant and employer, exact to the cent; the fee on the reimbursement comes from the claimant's money when it is enough. Optional prior-counsel fee split. No 130-week credit on SLU. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), 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": {
      "aww": "<aww>",
      "date_of_accident": "<date_of_accident>",
      "body_parts": "<body_parts>"
    },
    "name": "calculate_slu_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
awwYesAverage weekly wage before the injury, in dollars (gross).
body_partsYesEach scheduled member and its schedule loss of use percentage. Members: arm, hand, leg, foot, thumb, index/middle/ring/pinky finger, great toe, other toe, eye, one ear, both ears.
prior_paymentsNoOptional: dollars of this award already paid (0 if none). Adds the fee and net.
date_of_accidentYesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
prior_counsel_feesNoOptional. Dollar amount of the fee apportioned to each prior counsel (one or two). The current attorney gets the rest of the fee.
employer_reimbursementNoOptional employer reimbursement (REIMB ER) out of the award: { "amount": dollars } or { "amount_unknown": true } when it is still TBD. Needs prior_payments (0 if none).
weeks_at_temporary_totalNoOptional: weeks paid at temporary total, for the protracted healing period credit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare it as a safe, idempotent, closed-world read, yet the description still adds substantial behavior: a deterministic engine that never estimates, a 'missing' status path that returns every needed input and calculates nothing, conditional fee/rounding logic (15% rounded down to $5, OC-400.1), claimant-vs-employer money splitting, and return contents including citation flags and the not-legal-advice notice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The formula is front-loaded, but the single dense paragraph packs several run-on clauses, and the parenthetical '(the engine behind the app, the website calculators and the Pro Workspace)' is promotional filler that does not help an agent decide or call. The rest of the content largely 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?

Given 7 parameters, nested objects, and no output schema, the description covers the computation, the conditional branches, and the return payload (figures, rate year, cited formulas, notice) well. It stops short of describing the shape of a success payload or any non-'missing' failure path, which for a calculator with no output schema would have been useful.

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. The description still adds meaning: the protracted healing period credit is defined as weeks at temporary total beyond the longest healing period under §15(4-a), prior_counsel_fees is framed as a split where the current attorney receives the remainder, and the employer-reimbursement fee source ordering ('from the claimant's money when it is enough') clarifies a rule the schema only hints at.

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 (SLU award) with its exact formula and scope ('one or more scheduled members', 'New York State only', 'No 130-week credit on SLU'), which implicitly separates it from the ROM-percent and joint-replacement siblings by requiring a supplied loss_percent per body part.

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?

Clear about the conditions it applies to (scheduled members, NY only, no 130-week credit) and signals it never estimates, which distinguishes it from estimating paths. It does not explicitly name a sibling tool to use instead when the loss percentage must be derived from a ROM finding, so routing is left partly to inference.

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.