The Comp Desk Builder

NY third-party lien cost share (Burns/Kelly)

calculate_burns_lien

Read-onlyIdempotent

The carrier's equitable share of litigation costs on its workers' compensation lien when a third-party action recovers (WCL §29; Kelly; Burns): gross lien (indemnity + medical), the cost-share rate (attorney fee + disbursements ÷ gross recovery), the carrier's share and the net to the plaintiff. For a motor-vehicle case, give the no-fault threshold that comes off the lien first. 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. 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

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": {
      "gross_recovery": "<gross_recovery>",
      "indemnity_lien": "<indemnity_lien>",
      "medical_lien": "<medical_lien>",
      "attorney_fee": "<attorney_fee>",
      "disbursements": "<disbursements>"
    },
    "name": "calculate_burns_lien"
  }
}

Input Schema

Name	Required	Description
`attorney_fee`	Yes	Third-party attorney fee, in dollars.
`medical_lien`	Yes	Medical paid (lien), in dollars.
`disbursements`	Yes	Litigation disbursements, in dollars.
`gross_recovery`	Yes	Gross third-party recovery, in dollars.
`indemnity_lien`	Yes	Indemnity paid (lien), in dollars.
`motor_vehicle_threshold`	No	Optional, motor-vehicle cases: the amount that comes off the lien first, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: it never estimates, returns status "missing" with no calculation when an input is absent, requires a builder key, and returns formulas flagged for attorney review plus 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?

Front-loaded with the domain and the output list, then the mechanics, then the failure mode and auth requirement. Some sentences are promotional filler ('the engine behind the app, the website calculators and the Pro Workspace', 'matches the app to the cent') that could be trimmed without losing information.

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?

No output schema exists, so the description carries the burden and does so: it names every returned figure (figures, rate year, formulas with citations and review flags, disclaimer) and the missing-input response shape. For a deterministic six-parameter calculator, an agent has everything needed to call and interpret it.

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 baseline is 3, but the description adds genuine meaning: it defines gross lien as indemnity + medical and the cost-share rate as (attorney fee + disbursements) ÷ gross recovery, explaining how the parameters combine. It also clarifies the motor-vehicle threshold is deducted from the lien before the split, which the schema only hints at.

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: the carrier's equitable share of litigation costs on a NY workers' comp lien in a third-party action, citing WCL §29, Kelly and Burns. It enumerates the exact inputs and outputs (gross lien, cost-share rate, carrier's share, net to plaintiff), so an agent can distinguish it from siblings like calculate_apportionment or calculate_section_32_split 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?

Gives a clear condition for the optional parameter ('For a motor-vehicle case, give the no-fault threshold that comes off the lien first') and a hard scope limit ('New York State only'). It stops short of naming when to use a sibling calculator instead, so it is clear context without explicit exclusions.

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?