Skip to main content
Glama
Sign In

New York State Workers' Compensation Hub

by com.thecompdesk
OverviewDiscussionsAdmin

NY WC glossary term

define_term
Read-onlyIdempotent

A New York workers' compensation term from The Comp Desk glossary (AWW, SLU, LWEC, PFME, IME, ANCR, Section 32, CCP, form numbers and more): its meaning, detail, related terms and the source it comes from. Pass term for an exact entry, query to search, or nothing for the list.

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

Input Schema

NameRequiredDescriptionDefault
termNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds meaningful behavioral context beyond annotations by stating the content source and the returned information types. It does not describe not-found behavior or what happens if both term and query are supplied, leaving a small gap.

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

Conciseness5/5

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

The description is compact and front-loaded: it states the resource, useful examples, returned content, and usage modes in a small amount of text. The acronym examples add practical recognition value without becoming bloated.

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 simple two-parameter glossary lookup with rich annotations and no output schema, the description is largely complete. It explains the modes and the kind of result to expect. Minor gaps remain around ambiguous inputs and error behavior.

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 description coverage is 0%, so the description must carry parameter meaning. It does this well by mapping term to exact entry lookup, query to search, and absence of both to listing entries. It does not specify precedence when both term and query are provided, or matching behavior for query.

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?

The description clearly identifies a glossary lookup tool for New York workers' compensation terms and specifies the kinds of content returned: meaning, detail, related terms, and source. It provides concrete examples such as AWW, SLU, LWEC, and Section 32. It does not explicitly differentiate itself from closely related siblings like search_wc_knowledge or get_explainer, so it stops short of a 5.

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?

The description gives clear operational guidance: use term for an exact entry, query to search, or omit both to list entries. That is useful mode-selection context. It does not explicitly say when to use this tool instead of sibling knowledge or explainer tools, so it lacks the exclusion/alternative guidance needed for a 5.

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