warn-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WARN_MCP_TTL | No | Cache refresh interval in seconds (default behavior: at most one request per file per hour) | 3600 |
| WARN_MCP_CACHE | No | Override the cache directory (default: ~/.cache/warn-mcp) | ~/.cache/warn-mcp |
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_layoff_noticesA | Search US WARN Act mass-layoff notices across 48 states, 1988 to today, by employer name, state, date range and minimum headcount. Returns matched notice count, total workers affected, and the newest matching notices. Pass a state to make the search much faster. |
| latest_layoff_noticesA | The rolling feed of newly published WARN notices (the last ~14 days as the agencies posted them), newest first, optionally one state. Use this for 'what layoffs were announced recently'. |
| employer_layoff_historyA | Every WARN notice one employer has filed, in any covered state, back to 1988: notice count, total workers affected, states, first and latest activity, plus the individual notices for the best-matching employer. |
| state_layoff_totalsA | Monthly WARN notice counts and workers affected. With no state, returns a national leaderboard by state; with a state, the month-by-month series for it. Optionally restrict to one year. |
| agency_revisionsB | What the state agencies quietly CHANGED: a field-level diff of consecutive daily snapshots — corrected headcounts, moved dates, and notices the agency stopped publishing altogether. This history does not exist in any single-snapshot copy of the data. |
| dataset_statusA | Freshness and coverage of the dataset itself: when it was last rebuilt, which states are flagged stale, the license, and the raw endpoints. Call this before quoting a number so you can attribute it correctly. |
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 6 tools
Each tool targets a distinct aspect of WARN data: dataset health, searching, recent feed, employer history, state stats, and revision diffs. No two tools overlap in purpose; even the search and latest feed are clearly differentiated by time scope.
Names are all lowercase with underscores, which is consistent. However, the pattern mixes verb-led names (search_layoff_notices) with noun-led names (employer_layoff_history); while not chaotic, it's not a uniform verb_noun convention across the board.
Six tools is well-scoped for a domain-specific WARN server. Each tool covers a natural query pattern (status, search, recent, employer, state, revisions) without unnecessary bloat or an anemic surface.
The set covers core workflows: searching, recent notices, employer lookups, state aggregation, and data quality checks. Minor gaps might include fetching a single notice by ID or filtering by industry, but the existing tools handle most real-world queries without dead ends.