Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WARN_MCP_TTLNoCache refresh interval in seconds (default behavior: at most one request per file per hour)3600
WARN_MCP_CACHENoOverride 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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 (filters combine with AND; at least one is required). Returns matched_notices, matched_workers_affected and up to limit notices, newest notice_date first, each with id, state, company, location, employees_affected, notice_date, effective_date, notice_type and first_seen. Read-only, no key. For only the newest ~14 days use latest_layoff_notices; for one employer's whole record use employer_layoff_history.

latest_layoff_noticesA

The rolling feed of newly published WARN notices (the last ~14 days as the agencies posted them), newest notice_date first, optionally one state. Use this for 'what layoffs were announced recently'. Returns count_in_window plus up to limit notices in the same row shape as search_layoff_notices; for older dates or an employer filter use search_layoff_notices instead.

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. Returns employers_matched, employers (up to 10 distinct canonical names, most workers affected first) and notices_for_best_match (up to limit notices of the top employer, newest notice_date first). For a date- or state-bounded question use search_layoff_notices.

state_layoff_totalsA

Monthly WARN notice counts and workers affected. With no state, returns a national leaderboard by state in series (grouped_by=state, most workers affected first); with a state, the month-by-month series for it (grouped_by=month, oldest first). Optionally restrict to one four-digit year. totals carries overall notices and workers for the selection; notices without a published headcount count 0 workers. Aggregates only — use search_layoff_notices for the notices.

agency_revisionsA

Change log of the dataset itself: what differed between consecutive daily builds of the WARN notice table, since 2026-08-31. Each change is one of 'amended' (a tracked field of an existing notice changed — employees_affected, effective_date, location, notice_type, company, notice_date), 'row_absent' (a notice stopped appearing) or 'row_returned' (an absent notice came back). A change can come from the state agency amending or withdrawing a notice OR from an improvement to this project's parser; the log records the observation, never the cause, and cause_class labels only what is mechanically distinguishable (field_populated, field_cleared, format_only, value_changed, unknown). Filters combine with AND. Returns matched_changes, by_change_type, by_cause_class, log_covers_from/to, and up to limit changes newest observed_date first, each with id, state, company, notice_date, change_type, cause_class, field, old_value, new_value. Not a search for notices: use search_layoff_notices for notices and employer_layoff_history for one employer's full record.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool occupies a clearly distinct niche: general search, recent feed, employer history, state aggregates, dataset freshness, and change log. The descriptions explicitly cross-reference the other tools, so an agent can reliably pick the right one without ambiguity.

Naming Consistency4/5

All names use lowercase snake_case and follow a recognizable subject-prefix structure like search_, latest_, employer_, and state_. The only minor deviation is that search_layoff_notices is verb-led while most other names are noun phrases, but the pattern is still predictable.

Tool Count5/5

Six tools is well-scoped for a specialized WARN dataset server. Each tool earns its place by covering a distinct query mode or operational need, with no obvious redundancy or bloat.

Completeness4/5

The read-only domain is well covered: filtered search, recent notices, employer history, state totals, dataset status, and revision tracking are all present. Minor gaps exist, such as no direct lookup by notice id and no explicit pagination beyond `limit`, but agents can usually work around these with the available search and history tools.

Maintenance

ActivityMaintained
ResponsivenessNo issues