mcp-wagewatch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOL_API_KEY | Yes | Your DOL Open Data API key. Register at https://dataportal.dol.gov/registration |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| employer_violationsA | Search WHD enforcement cases by employer name (matches trade name or legal name), optionally filtered to a state. Returns each case with location, findings dates, back wages, civil penalties, and employees affected. Ordered by back wages (largest first). |
| back_wages_summaryA | Aggregate total back wages, employees affected, civil penalties, and case count for an employer-name and/or state query. Computed client-side over up to 1000 matching cases. At least one of employer or state is required. |
| violations_by_stateA | Top WHD enforcement cases in a state (cases where a violation was found), ordered by back wages owed. Optionally filter to an industry by NAICS code prefix (e.g. "72" for accommodation and food services). |
| case_detailA | Full record for one WHD enforcement case by its case id, including the per-statute breakdown (which labor laws were violated: FLSA, MSPA, H-1B, FMLA, Davis-Bacon, child labor, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: employer_violations searches by employer name, back_wages_summary provides aggregate statistics, violations_by_state lists top cases in a state with optional industry filter, and case_detail gives full details for a specific case. No overlap in functionality.
All tool names use consistent snake_case format and follow a clear pattern: noun_descriptor (employer_violations, back_wages_summary, case_detail) and noun_by_noun (violations_by_state). There is no mixing of conventions or confusing naming.
With 4 tools, the server is well-scoped for the domain of WHD enforcement cases. Each tool serves a necessary function (search, aggregate, state-level view, detail) without being too few or too many.
The tool surface covers the essential operations for the domain: searching by employer, viewing top cases by state, getting aggregate summaries, and retrieving full case details. There are no obvious gaps or dead ends; the tools work together to provide a complete workflow.