Skip to main content
Glama

New York State Workers' Compensation Hub

NY award for benefit periods, full CCP engine

calculate_ccp_award_detailed
Read-onlyIdempotent

The full Pro Workspace CCP / Award engine: periods of type TT (total), RE (reduced earnings, with current weekly earnings), TR / TP (a disability percentage of two-thirds of the wage, or a typed weekly rate), NCLT / NME ($0) and HIA (held in abeyance, no weeks); weeks counted with both ends, the shared boundary day once, rounded down to none / tenth / whole (default tenth); each rate within the max and min for the date of accident (RE capped, never raised); an amending period paid at its rate less a prior percentage or prior weekly rate; already-paid periods kept in the award but out of the money moving and fee; employer reimbursements per period with scope "period", "all" or a "specific" date range (or amount unknown); the CCP fee (the weekly CCP amount ÷ 3); prior payments; and the prior-counsel split. Returns every period, the award, the exact fee, the OC-400.1 amount rounded down to $5 and both nets. calculate_ccp_award is the simpler TT/TP/RE version. 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": {
      "aww": "<aww>",
      "date_of_accident": "<date_of_accident>",
      "periods": "<periods>"
    },
    "name": "calculate_ccp_award_detailed"
  }
}

Input Schema

NameRequiredDescriptionDefault
awwYesAverage weekly wage, in dollars.
periodsYes
prior_paymentsNoOptional: dollars already paid on these periods.
weeks_roundingNoOptional; default tenth.
date_of_accidentYesDate of accident. YYYY-MM-DD.
ccp_weekly_amountNoOptional: the weekly CCP amount; its fee is the amount ÷ 3.
prior_counsel_feesNoOptional: each prior counsel's dollar share of the fee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the bar is low, yet the description adds substantial context: computation runs on calc-core and "never estimates," a missing input returns status "missing" with nothing calculated, and the response includes per-step rules, engine function names, and a not-legal-advice notice. This tells the agent what to expect on both success and failure paths.

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?

It is front-loaded with the identifying phrase and every clause carries real information, but the bulk is a single sprawling semicolon-chained sentence that is hard to scan. The content earns its place; the structure does not.

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 genuinely complex calculation tool with seven parameters, no output schema, and a nested periods array, the description covers inputs, period-type semantics, rounding, capping, fee math, and the full return payload including both nets. Nothing an agent needs in order to invoke it correctly 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 already 86%, so the baseline is 3; the description earns above that by adding rules the schema does not state — weeks counted with both ends and the shared boundary day once, RE rates capped but never raised to the min, fee = weekly CCP ÷ 3, OC-400.1 rounded down to $5, and the three employer-reimbursement scopes. It stops short of 5 because the prose is not mapped cleanly to individual parameters.

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 specific engine and enumerates exactly which period types (TT, RE, TR/TP, NCLT/NME, HIA) it handles, then explicitly distinguishes itself from the sibling: "calculate_ccp_award is the simpler TT/TP/RE version." An agent can tell the two apart without opening either 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?

It gives a clear routing rule against the sibling and a hard scope constraint ("New York State only"). What's missing is an explicit when-not statement beyond the implied 'use the simpler tool if you only need TT/TP/RE' — the agent must infer that condition rather than read it stated.

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.