Skip to main content
Glama
Sign In

New York State Workers' Compensation Hub

by com.thecompdesk
OverviewDiscussionsAdmin

NY WCB form: what it is for

lookup_wcb_form
Read-onlyIdempotent

What a New York Workers' Compensation Board form is (for example C-3, C-4, C-4.3, RB-89, OC-400.1), from The Comp Desk's approved glossary and knowledge base, with the Board's link. A form not in those sources is reported as not covered, with the Board's forms page.

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": {
      "form": "<form>"
    },
    "name": "lookup_wcb_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
formYesThe form number, e.g. "C-3" or "RB-89.1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and openWorldHint=false, and the description is consistent with that closed-world framing by naming the two internal sources. It adds genuinely new behavior: the response carries the Board's link, and uncovered forms get an explicit not-covered result plus a pointer to the Board's forms page, so an agent knows the failure mode is a normal answer rather than an error.

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?

Two sentences, front-loaded with the purpose and followed by the coverage/fallback rule. Dense but no filler; the parenthetical examples are load-bearing for format inference.

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 one-parameter lookup with no output schema and full safety annotations, this covers what is needed: what it returns (what the form is for, plus the Board's link) and what happens when the form is unknown. Nothing essential for correct invocation is missing, though the shape of the returned entry (field names, length) is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'form' parameter already carries examples ('C-3' or 'RB-89.1'), so the schema does the work. The description reinforces the expected format by listing additional variants (C-4.3, OC-400.1), which is mildly additive but not new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a specific verb-and-resource pair ('what a New York Workers' Compensation Board form is'), gives concrete form numbers (C-3, C-4.3, RB-89, OC-400.1), and pins the source ('approved glossary and knowledge base'). It stops short of naming the sibling it is not -- define_term is a nearby glossary lookup, and the description never draws that boundary -- so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for 'what is form X for' questions, and the description usefully states the coverage boundary (a form not in the sources is reported as not covered, with the Board's forms page). There is no explicit when-to-use versus define_term or search_wc_knowledge, and no stated preconditions.

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

All New York State Workers' Compensation Hub toolsInspect
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