Skip to main content
Glama

New York State Workers' Compensation Hub

NY SLU % from range of motion

calculate_slu_percent_from_rom
Read-onlyIdempotent

A schedule loss of use percentage range from measured range of motion, scored by the app's SLU range-of-motion engine (2018 NY Impairment Guidelines): each joint's deficit by severity band with proportional adjustment, the paired-motion rule (both_motions), the ankylosis cap for the body part, an optional special consideration (added or stand-alone, as the engine marks it), an optional contralateral baseline, and the shoulder muscle-atrophy finding. Joints per body part: Thumb IP/MCP/CMC (CMC is the opposition grade 1–3), Finger DIP/PIP/MCP, Wrist Palmar Flex/Dorsi Flex/Pron/Sup, Elbow Extension/Flexion, Shoulder Forward Flexion/Abduction/Int Rotation/Ext Rotation/Adduction/Post Extension, Hip Abduction/Adduction/Int Rotation/Ext Rotation/Flexion/Post Extension, Knee Flexion/Extension, Ankle/Foot Plantar Flex/Dorsi Flex/Inversion/Eversion, Great Toe IP/MTP Flex/MTP Ext, Smaller Toes DIP/PIP/MTP. Returns a percentage, not an award: pass the percentage to calculate_slu_award. 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": {
      "body_part": "<body_part>",
      "measurements": "<measurements>"
    },
    "name": "calculate_slu_percent_from_rom"
  }
}

Input Schema

NameRequiredDescriptionDefault
body_partYes
both_motionsNoOptional: joints whose paired motion (extension, supination) is also deficient, so the higher figure applies.
measurementsYesJoint name → measured degrees (Thumb CMC: opposition grade 1, 2 or 3). Joint names exactly as listed in the description.
contralateralNoOptional: joint name → the uninjured side's degrees, used as the baseline.
special_considerationNoOptional: a special consideration label exactly as the engine lists it for this body part (an invalid label returns the allowed list).
shoulder_muscle_atrophyNoOptional, shoulder: a muscle-atrophy finding (gates the marked-rotation add).

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?

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds substantial context: the computation is deterministic ('it never estimates'), it names the shared engine, and it discloses the return shape (figures, per-step rule and engine function, not-legal-advice notice) and the 'missing' status on absent inputs. That is meaningful behavioral disclosure beyond the structured fields.

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?

Purpose is front-loaded and the long joint enumeration is load-bearing because the schema references it. However, the engine is introduced twice ('scored by the app's SLU range-of-motion engine' and then 'Computes with The Comp Desk calc-core, the same engine as the app'), which is redundant in an already dense single paragraph.

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 six-parameter tool with a nested free-form measurement map and no output schema, the description covers the computation model, the valid joint vocabulary, the optional inputs' effects, the return contents, and the error behavior. An agent has everything needed to call it correctly and to interpret the result.

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 83%, so the schema already carries most parameter meaning, and the description still adds real semantics: it enumerates the joints valid per body part (the schema defers to it: 'Joint names exactly as listed in the description'), explains both_motions as the paired-motion rule, the special-consideration add/stand-alone behavior, the contralateral baseline, and the shoulder atrophy gating of the marked-rotation add. The enumeration is what makes the free-form measurements object usable.

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 — computing a NY schedule-loss-of-use percentage range from measured range of motion — and names the exact engine and guideline set behind it. It explicitly separates itself from calculate_slu_award ('returns a percentage, not an award: pass the percentage to calculate_slu_award'), so 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?

Gives clear routing guidance ('pass the percentage to calculate_slu_award') and a hard scope boundary ('New York State only'), plus the failure condition (missing input → status 'missing', nothing calculated). It does not name when an agent should prefer calculate_slu_joint_replacement or other SLU variants, so it falls short of full when-not coverage.

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.