Skip to main content
Glama
Sign In

New York State Workers' Compensation Hub

by com.thecompdesk
OverviewDiscussionsAdmin

My hearing notes waiting to be posted

list_hearing_notes
Read-onlyIdempotent

Signed-in Pro or Firm attorneys only. Lists the hearing notes the attorney formatted in THEIR OWN Comp Desk Pro Workspace and sent with "Post Hearing Notes in Case Management OS via Claude" (drafts never appear): for each, the id, case label, WCB number, hearing date, purpose, WCLJ, WCB status (HS / NFA / FTP), the system the attorney chose, how many to-dos it has, the next date, and whether it is queued or already posted. Newest hearing first. Call it to find the notes to post, then get_hearing_note for each. Notes are client-confidential: use them only for that entry.

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

Input Schema

NameRequiredDescriptionDefault
toNoOptional. Latest hearing date, YYYY-MM-DD.
fromNoOptional. Earliest hearing date, YYYY-MM-DD.
limitNoAt most this many (default 20).
statusNoqueued (default): waiting to be posted. entered: already posted. all: both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond that: an authorization gate (Pro/Firm attorneys only), the fact that unsent drafts are invisible, newest-hearing-first ordering, and a client-confidentiality handling constraint. It does not describe result volume or pagination behavior beyond the schema's limit, which keeps it short of a 5.

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 access gate, then the scope, then the field list and the next-step routing sentence; every clause carries information. The middle field enumeration is dense but earns its place because no output schema exists to document return shape.

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?

With no output schema, the description must carry the return shape, and it does: id, case label, WCB number, hearing date, purpose, WCLJ, WCB status codes, chosen system, to-do count, next date, and posted state. Combined with the auth and confidentiality notes, an agent has everything needed to call it and interpret results.

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 all four parameters carry their own descriptions with formats, defaults, and enum values, so baseline is 3. The description's mention of 'whether it is queued or already posted' loosely maps to the status filter but adds no new syntax or usage nuance for from/to/limit.

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 (list hearing notes) plus precise scope: notes the signed-in attorney formatted in THEIR OWN Comp Desk Pro Workspace and sent explicitly, drafts excluded. It enumerates the returned fields and ordering (newest hearing first), so an agent can distinguish it from get_hearing_note and the calculator siblings 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 Guidelines5/5

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

Gives an explicit call sequence: 'Call it to find the notes to post, then get_hearing_note for each,' naming the sibling consumed downstream. It also states prerequisites (signed-in Pro or Firm attorneys) and an exclusion (drafts never appear), leaving little to inference.

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