Skip to main content
Glama

Warn Recent

warn_recent
Read-onlyIdempotent

Most recent US WARN Act layoff and plant-closure notices across every covered state, newest first, the earliest public signal that an employer is cutting jobs, filed roughly 60 days before the layoff takes effect. Answers "recent layoff notices", "who announced layoffs this month", "latest WARN filings in Texas". Returns employer, site, worker count and effective date, plus states_covered so a quiet month is distinguishable from a coverage gap.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": 30
    },
    "name": "warn_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook back this many days from today by WARN notice date (default 30).
limitNoMax notices to return (default 50, max 500).
stateNoTwo-letter state code to restrict to, e.g. "NY". Omit for all covered states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, open world), so the description's additional value is the ordering guarantee ('newest first'), the ~60-day filing lead time, and the states_covered field that flags a coverage gap rather than a genuinely quiet month. These are traits the annotations do not carry. It does not state rate limits or pagination beyond the schema's limit.

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?

Information is front-loaded: scope and ordering come first, then the timing rationale, then example questions and return fields. The middle clause ('the earliest public signal...') is dense but earns its place by explaining why the data matters.

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 steps in by naming the returned fields (employer, site, worker count, effective date, states_covered) and explains the coverage caveat. Ordering, time window and defaults are all covered, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so defaults and semantics for days, limit and state are already fully documented, giving a baseline of 3. The description reinforces the date-window concept ('newest first', 'this month') but adds no syntax or edge-case detail beyond the schema.

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?

States a specific verb and resource, 'Most recent US WARN Act layoff and plant-closure notices across every covered state, newest first', and adds the substantive framing that these are public signals filed ~60 days ahead of the layoff. That timing detail alone lets an agent distinguish it from a generic search tool.

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?

Example phrasings ('recent layoff notices', 'who announced layoffs this month', 'latest WARN filings in Texas') give concrete conditions for choosing this tool over a lookup of a particular employer. No explicit exclusions or named alternative (warn_search, warn_company) are given, so a gap remains.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.