Skip to main content
Glama

New York State Workers' Compensation Hub

NY radiculopathy severity rank

rank_radiculopathy
Read-onlyIdempotent

The cervical or lumbar radiculopathy severity ranking, scored the way the Pro Workspace Radiculopathy tile scores it, from the 2012 NYS Impairment Guidelines tables as calc-core carries them: imaging 16, EMG 6, muscle weakness by grade (0–1: 20, 2: 18, 3: 6, 4–5: 0) plus atrophy 6 under the root's weakness cap, sensory (compromised 4, anesthesia 6) under the root's sensory cap, reflex (diminished 4, absent 6), tension signs 4; the letter from Table S11.7. Give the findings (unlisted findings count as normal / no), or instead total_points to rank a total already scored. A total with no row on Table S11.7 (1–3 points, or above the top row) is refused with the reason, never given a letter. Cervical roots C5–T1, lumbar L3–S1. 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": {
      "region": "<region>"
    },
    "name": "rank_radiculopathy"
  }
}

Input Schema

NameRequiredDescriptionDefault
emgNoEMG fibrillations / positive sharp waves in 2+ muscles of the root.
reflexNo
regionYes
imagingNoImaging shows nerve-root displacement or encroachment that correlates.
sensoryNo
nerve_rootNo
total_pointsNoInstead of the findings: a total already scored, to rank.
tension_signsNoSpurling's, straight leg raise or femoral stretch positive.
muscle_atrophyNo
muscle_weakness_gradeNoMotor grade 0–5; default 5 (normal).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses refusal behavior for off-table totals, the 'missing' status when an input is absent, the default that unlisted findings count as normal/no, deterministic non-estimating execution via calc-core, and what the response contains (figures, rule-backed steps, not-legal-advice notice). Nothing here contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core identity is front-loaded, but the bulk is delivered as one long semicolon-chained sentence whose dense point tables are hard to scan. The content mostly earns its place, yet it would read far better split into short labeled statements (scoring, input modes, refusals, output).

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 10-parameter tool with no output schema, the definition covers jurisdiction, supported root ranges (C5–T1, L3–S1), default handling, refusal cases, and return composition — enough to call it correctly. Gaps are minor: no detail on rounding/validation of total_points or on region/root consistency.

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?

With only 50% schema coverage across 10 params, the description compensates well: it maps point values onto imaging, EMG, weakness grades 0–5, atrophy, sensory states, reflex states, and tension signs, and explains total_points as a pre-scored alternative to findings. It does not clarify how region and nerve_root must agree (e.g. a lumbar root with cervical region), leaving one interaction implicit.

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 — ranking cervical/lumbar radiculopathy severity under the 2012 NYS Impairment Guidelines Tables — and pins the exact scoring model (S11.7 letter, per-finding point values). An agent can distinguish it from calculation siblings such as calculate_slu_percent_from_rom or calculate_ccp_award without opening a 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?

Explicitly offers two input modes: 'Give the findings ... or instead total_points to rank a total already scored,' and states the scope boundary 'New York State only.' It also names an exclusion (a total with no Table S11.7 row is refused rather than given a letter), though it does not name an alternative tool for out-of-scope or non-NY cases.

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.