The Comp Desk Builder

get_formula

The real NYS WC formula catalog behind the Comp Desk calculators: algebraic form, symbol table (what every symbol means), plain-language explanation, statutory/case citation, and a per-entry verified flag. Served from the SAME module the Pro Workspace shows, so the API and the app cannot disagree. Filter by id, by group (aww, rate, slu, lwec, perm, settle, fee), or by a free-text term; omit everything for the whole catalog. An entry with verified:false has NOT been through legal review — never present its citation as settled law.

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

Input Schema

Name	Required	Description	Default
`q`	No
`id`	No
`group`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does so well: it discloses that data comes from the same module as the Pro Workspace so API and app agree, and it spells out the consequence of verified:false including an explicit instruction never to present an unreviewed citation as settled law. It leaves gaps around auth requirements and what happens with an unfiltered whole-catalog call (volume/pagination).

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?

Three sentences, the resource description front-loaded, then filtering options, then the critical verified-flag caveat placed last where it stands out. Slight overhead in the promotional 'The real ... behind the Comp Desk calculators' framing, but no sentence is truly wasted.

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?

There is no output schema, and the description compensates by enumerating the returned fields (form, symbol table, explanation, citation, verified flag). Remaining gap is behavior on a full-catalog request, which could be large, and whether results are paginated or truncated.

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 0%, so the description must compensate, and it does: it explains q as a free-text term, id as an entry selector, enumerates all seven group values, and defines the omit-all default. It adds no detail on id formatting (slug vs numeric) or how q and group combine when both are supplied.

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 names a specific resource (the NYS WC formula catalog) and enumerates its content: algebraic form, symbol table, plain-language explanation, citation, and verified flag. That distinguishes it from the calculation siblings, which compute numbers rather than return reference entries, so an agent can tell what it gets without inspecting 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 Guidelines4/5

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

It explicitly states the three ways to narrow the catalog (id, group, free-text term) and that omitting everything returns the whole catalog, which is clear usage context. It does not explicitly say when to prefer this over the calculate_* siblings or the reference tool, so routing guidance is implied rather than stated.

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?