Skip to main content
Glama

New York State Workers' Compensation Hub

NY award for benefit periods (CCP)

calculate_ccp_award
Read-onlyIdempotent

What is owed for one or more benefit periods (types TT total, TP partial with a disability %, RE reduced earnings with weekly earnings), the way The Comp Desk's CCP/Award calculator works it out: weeks from the dates (both ends count; a period starting the day the last ended counts it once; weeks rounded down to the tenth by default), each period's rate within the max and min, and the total award. With prior_payments (0 if none) it adds the claimant's money, the 15% fee exact to the cent, the OC-400.1 amount rounded down to $5 and the net; an employer reimbursement out of the whole award is split as 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>",
      "periods": "<periods>"
    },
    "name": "calculate_ccp_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
awwYesAverage weekly wage before the injury, in dollars (gross).
periodsYes
prior_paymentsNoOptional: dollars already paid on these periods (0 if none). Adds the fee and net.
weeks_roundingNoOptional; default tenth.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds real behavioral detail: missing inputs return status "missing" and compute nothing, weeks count both ends and round down to a tenth by default, prior_payments triggers the 15% fee, the OC-400.1 rounding to $5, and net computation. It also discloses the return shape (figures, rate year, cited formulas with attorney-review flags, not-legal-advice notice) and the guarantee that it never estimates.

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 leading sentence is front-loaded with the scope and the period types before the mechanics. It is dense and somewhat run-on with stacked parentheticals, and the 'engine behind the app, the website calculators and the Pro Workspace' clause is promotional padding, but almost every remaining clause carries operational meaning.

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?

With seven parameters, nested period objects and no output schema, the description does the work an output schema would have done: it names the return fields, the rate year, citation flags and the notice, plus the missing-input failure mode. The one notable hole is disambiguation from calculate_ccp_award_detailed and from the individual rate/weeks calculators.

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 86%, so the baseline is 3, and the description earns extra by explaining the consequences of optional parameters the schema only names: prior_payments (0 if none) adds the claimant's money, the exact 15% fee and the $5-rounded OC-400.1 amount; employer reimbursement is split as on SLU and requires prior_payments. It also documents the default weeks_rounding behavior, which the schema labels only as 'default tenth'.

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?

States a specific computation (what is owed for one or more benefit periods) with the three period types spelled out (TT/TP/RE) and the jurisdiction (New York State only). An agent can tell this is an award calculator rather than a rate or weeks calculator, but the description never distinguishes it from the very similar sibling calculate_ccp_award_detailed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: use it to compute an award given AWW, accident date and periods, plus optional prior payments for fee/net math. There is no explicit 'when not to use' and no routing to calculate_ccp_award_detailed or calculate_benefit_weeks, which matters given how close those siblings are. The 'New York State only' constraint is the one clear scoping rule.

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.