Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_workers_comp_ppd_rating

Calculate workers' comp permanent partial disability awards from scheduled body part weeks, impairment rating, and average weekly wage to determine statutory compensation weeks and total cash payout.

Instructions

Workers' Comp Permanent Partial Disability (PPD) Rating & Schedule. Calculate scheduled body member permanent partial disability (PPD) statutory compensation weeks, impairment ratings, and total cash award. Discipline: LEGAL. Governing mathematical model / formula: Total PPD Award = (Scheduled Weeks for Body Part) × (Impairment Rating %) × (Weekly Statutory Compensation Rate).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_ppd_award_usd (Total Permanent Disability Award), statutory_weekly_rate (Statutory Weekly PPD Rate (66.6%)), compensated_weeks_count (Compensated Benefit Weeks), statutory_rate_cap_status (State Maximum Cap Status) using average_weekly_wage_aww (Pre-Injury Average Weekly Wage ($ AWW)), physician_impairment_rating_pct (Doctor Permanent Impairment Rating (%) in %), scheduled_body_part_weeks (Scheduled Body Part Statutory Weeks in weeks). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Workers' Comp Permanent Partial Disability (PPD) Rating & Schedule' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "workers-comp-ppd-rating"

    • category (string): "legal"

    • name (string): "Workers' Comp Permanent Partial Disability (PPD) Rating & Schedule"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_ppd_award_usd (Total Permanent Disability Award): Formatted display string (e.g. '$23,000.00')

      • metrics.statutory_weekly_rate (Statutory Weekly PPD Rate (66.6%)): Formatted display string (e.g. '$766.67 / week')

      • metrics.compensated_weeks_count (Compensated Benefit Weeks): Formatted display string (e.g. '30.0 Weeks')

      • metrics.statutory_rate_cap_status (State Maximum Cap Status): Formatted display string (e.g. 'Under State Maximum Cap')

    • execution_time_ms (number): Latency in milliseconds.

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": "omni_workers_comp_ppd_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
average_weekly_wage_awwNoPre-Injury Average Weekly Wage ($ AWW). Gross weekly wages earned prior to workplace injury. Default: 1150. Min: 200. Max: 5000.
scheduled_body_part_weeksNoScheduled Body Part Statutory Weeks (weeks). Arm = ~250-312 wks, Leg = ~200-288 wks, Hand = ~160-244 wks, Eye = ~120-160 wks. Default: 200. Min: 20. Max: 500.
physician_impairment_rating_pctNoDoctor Permanent Impairment Rating (%) (%). AMA Guides to Permanent Impairment percentage. Default: 15. Min: 1. Max: 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are supplied, so the description must carry the safety profile; it does by declaring read-only, idempotent, stateless execution with zero side effects and no persistent state. It also discloses input-bound validation and safe diagnostic errors rather than runtime exceptions, plus the structured return shape.

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 definition is front-loaded and organized into purpose, usage, safety, and returns, with little wasted prose. It is longer than necessary in places, repeating the title and formula across sections, but the structure keeps it navigable.

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?

For a three-parameter deterministic calculator with no output schema, the description gives the formula, input roles, validation behavior, and a detailed return object including all computed metrics. The main remaining gap is that statutory cap status is described as an output without explaining how the cap is determined.

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, but the description adds the calculation relationship among AWW, impairment rating, scheduled weeks, and the 66.6% statutory weekly rate. It does not explain cap determination or edge-case jurisdiction logic, so it is not a 5.

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 verb and resource: calculates Workers' Comp PPD statutory weeks, impairment ratings, and total cash award. It gives the governing formula and distinguishes the tool from the generic omni_universal_query dispatcher, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE and WHEN NOT TO USE sections define the deterministic numerical calculation case and exclude qualitative or unquantified reasoning. SIBLING ROUTING names omni_universal_query as the generic alternative and directs cross-discipline dispatch there.

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

Deploy Server

Other Tools