Skip to main content
Glama

New York State Workers' Compensation Hub

NY LWEC / non-schedule PPD award

calculate_lwec_award
Read-onlyIdempotent

A permanent partial disability (non-schedule) award from a loss of wage-earning capacity percentage: the weekly rate (the bounded two-thirds rate × the LWEC %, kept within the max and min), the number of weeks for that LWEC bracket (§15(3)(w): 225 to 525 weeks depending on the bracket), the award, and, with the weeks of temporary benefits already paid, the credit for weeks beyond 130. 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>",
      "lwec_percent": "<lwec_percent>"
    },
    "name": "calculate_lwec_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
awwYesAverage weekly wage before the injury, in dollars (gross).
lwec_percentYesLoss of wage-earning capacity, 0–100 (50 means 50%).
date_of_accidentYesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
prior_temporary_weeksNoOptional: weeks of temporary benefits already paid (for the 130-week credit).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/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), and the description adds substantial context beyond them: the calc-core engine, the explicit 'never estimates' guarantee, the missing-input contract, and the return payload including attorney-review flags and the not-legal-advice notice. This is behavior an agent could not infer from the structured fields.

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?

The purpose is front-loaded in the opening clause, and each subsequent sentence carries distinct information (engine, missing-input behavior, return contents). The first sentence is heavily nested with parentheticals and dashes, which makes it dense to parse, but there is no filler.

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?

With no output schema, the description carries the return-value burden and does so fully: figures, rate year used, cited formulas with review flags, the not-legal-advice notice, and the 'missing' status shape. Nothing needed to call or interpret this four-parameter calculator is 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 100%, so the baseline is 3; the description goes further by explaining how the inputs combine — the bounded two-thirds rate multiplied by the LWEC percentage and clamped to max/min, and how prior temporary weeks drive the credit beyond 130 weeks. It adds computational meaning rather than restating field definitions.

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 on a specific resource: a NY permanent partial disability (non-schedule) LWEC award, and enumerates the outputs (weekly rate, weeks for the bracket, award, 130-week credit). 'Non-schedule' plus the §15(3)(w) bracket reference distinguishes it from the schedule-loss tools such as calculate_slu_award without naming them.

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?

The scenario that selects this tool is clear — non-schedule PPD in New York only — and it states the failure mode (missing input returns status 'missing' and nothing is computed). It does not explicitly name the sibling alternatives (e.g., weekly-rate or schedule-loss calculators) or say when not to use it, so it stops short of full routing guidance.

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.