Skip to main content
Glama

Workers' Rights

by com.workers-rights
OverviewDiscussionsAdmin

Explain applicable employment-law rights

explain_my_rights
Read-only

Explain which federal (and state, if a state is given) employment laws may protect a worker based on the type of issue (e.g. discrimination, harassment, retaliation, wrongful termination) and/or the protected class involved (e.g. race, sex, age, disability, pregnancy). Returns the relevant statutes with citations, who they cover (employer-size thresholds), filing deadlines and agencies, and available remedies. Use this to ground an answer about a worker’s legal protections. Deadline guidance covers private-sector and state/local government workers; federal employees follow a separate process with a much shorter deadline (45 days to contact their agency's EEO counselor). Educational information, not legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueNoType of workplace issue, e.g. "discrimination", "harassment", "retaliation", "wrongful termination", "unpaid wages", "disability accommodation".
stateNoUS state (2-letter code or full name) to include state-specific protections and the correct EEOC filing deadline.
employer_sectorNoWhether the employer is private, state/local government, or a federal agency.
protected_classNoProtected characteristic involved, e.g. "race", "sex", "age", "disability", "religion", "national origin", "pregnancy".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / employer_sector
      Added value: +{
+  "description": "Whether the employer is private, state/local government, or a federal agency.",
+  "enum": [
+    "private",
+    "government",
+    "federal_government"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate a safe, read-only, non-destructive operation, and the description adds meaningful behavioral context beyond that: it is educational information rather than legal advice, and it discloses a critical exception for federal employees with a 45-day EEO counselor deadline. This gives the agent important limitations and caveats that annotations alone cannot convey.

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?

The description is moderately long but front-loaded with the core purpose and return value before the usage caveats and disclaimer. Every sentence earns its place given the legal complexity; it could be slightly tighter, but there is no filler.

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 takes on the burden of explaining what the tool returns, which it does thoroughly: statutes, citations, employer-size thresholds, filing deadlines, agencies, and remedies. It also covers parameter-specific exceptions and the educational nature of the output, making it complete enough for an agent to invoke correctly.

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 100%, so the baseline is 3, but the description adds value by showing how parameters interact: state is only relevant when provided, and employer_sector maps to the federal-employee exception with a separate deadline. It also gives concrete examples for issue and protected_class that reinforce the schema descriptions.

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 uses a specific verb and resource: explaining applicable employment-law rights based on issue and/or protected class. It clearly distinguishes this tool from procedural or attorney-search siblings by specifying that it returns statutes, citations, coverage thresholds, deadlines, agencies, and remedies.

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 explicitly tells the agent to use this tool to ground an answer about a worker's legal protections, giving clear context for when it applies. It does not name alternatives or state when not to use it, so it falls just short of full routing guidance.

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

All Workers' Rights 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