Skip to main content
Glama
Sign In

New York State Workers' Compensation Hub

by com.thecompdesk
OverviewDiscussionsAdmin

NY maximum and minimum weekly benefit

get_max_min_rate
Read-onlyIdempotent

The New York maximum and minimum weekly workers' compensation benefit for a date of accident (the rate year runs July 1 to June 30; the maximum is fixed by the date of accident, never by today's date). Use for "what is the max rate for a 2025 injury". 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": {
      "date_of_accident": "<date_of_accident>"
    },
    "name": "get_max_min_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_of_accidentYesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.

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?

The annotations already say the tool is read-only, idempotent, closed-world and non-destructive, but the description goes well beyond them. It says the figures come from the calc-core engine and are never estimated, that a missing input returns a 'missing' status with the list of inputs still needed, and that a result includes the rate year, the formulas with attorney-review flags, and a 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.

Conciseness4/5

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

The content is front-loaded: scope and jurisdiction come first, followed by output expectations. It is a single dense paragraph with some parenthetical asides (calc-core origins, attorney-review flags) that are useful but make it longer than strictly necessary.

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?

There is no output schema, and the description makes up for that by spelling out the return contents (figures, rate year, formulas with citations, disclaimer) and the missing-input behavior. For a single-parameter lookup tool with fully covered schema, nothing an agent needs in order to call 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 100% and there is a single parameter, so the baseline would be 3. The description adds real meaning that the schema does not: the rate year runs July 1 to June 30, and the applicable rate is fixed by the date of accident rather than today's date, which is exactly the interpretive point an agent needs for this parameter.

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 specific verb and resource: the New York maximum and minimum weekly workers' compensation benefit for a given date of accident. It also scopes the tool to one jurisdiction ('New York State only') and contrasts computing a rate with estimating one, so an agent can tell it apart from generic rate calculators in the sibling list.

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 concrete when-to-use example ('what is the max rate for a 2025 injury'), says the maximum is fixed by the date of accident and never by today's date, and restricts scope to New York. It does not name the alternative for other states or point to calculate_weekly_rate, so there are no explicit exclusions; that is why this is a 4 rather than a 5.

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

All New York State Workers' Compensation Hub toolsInspect
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