The Comp Desk Builder

NY notice-to-employer deadline

get_notice_deadline

Read-onlyIdempotent

The date written notice of the injury to the employer is due under the NY Workers' Compensation Law, counted from the date of accident, or from the date of disablement for an occupational condition that built up over time, with the days left from today in New York and the statute it comes from. New York State only; not a substitute for checking the facts. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notice_deadline"
  }
}

Input Schema

Name	Required	Description	Default
`date_of_accident`	No	Date of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
`date_of_disablement`	No	For an occupational condition: date of disablement, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read. The description adds context the annotations cannot carry: the result is derived from the statute, 'days left' is computed relative to today in New York, and a builder key is required for auth. It stops short of stating what happens if no date is supplied, so it is strong but not exhaustive.

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 core definition is front-loaded in the first sentence and the scope/auth caveats follow in short clauses, so there is little wasted reading. The closing claim about matching the app 'to the cent' via CD.Calc is promotional padding that does not help an agent decide or invoke.

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 burden of describing returns and does so: the due date, the days remaining, and the originating statute. For a two-optional-parameter read-only calculator this covers everything an agent needs to call it competently, aside from the both-parameters-absent edge case.

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 adds real meaning on top by explaining the either/or logic: the clock runs from the accident date, or from the disablement date for an occupational condition that built up over time. It does not clarify that at least one of the two optional parameters must be provided, which is the remaining semantic gap.

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 states a precise verb and resource: it returns the date written notice of injury to the employer is due under NY Workers' Compensation Law. It also names the computation basis (date of accident or date of disablement) and the extra outputs (days left, statute), which clearly separates it from the sibling calculate_* tools.

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?

It scopes usage to New York State only and warns it is not a substitute for checking the facts, which is genuine boundary guidance. However, it never says when to prefer this over a sibling calculator or what to do when only one of the two dates is known, so the when-to-use guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Comp Desk Builder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?