Skip to main content
Glama

Warn Company

warn_company
Read-onlyIdempotent

Every WARN Act layoff and closure notice one employer has filed, across all covered states, with a per-state and per-year breakdown. Answers "has Tesla filed layoff notices", "how many workers has Amazon laid off by WARN filing", "which sites did this company close". Use to trace one employer's layoff history rather than browsing a date range.

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": {
      "company": "Genentech"
    },
    "name": "warn_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax notices to return (default 200, max 500).
companyYesEmployer name, free text, "Tesla" matches "Tesla, Inc." and "TESLA MOTORS".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Employer name, free text — \"Tesla\" matches \"Tesla, Inc.\" and \"TESLA MOTORS\"."New value: +"Employer name, free text, \"Tesla\" matches \"Tesla, Inc.\" and \"TESLA MOTORS\"."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely new context: results are aggregated per state and per year, coverage spans all covered states, and it doubles as a closure/site-discovery source — useful since there is no output schema.

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?

Front-loaded with the scope statement, followed by example questions and then the routing rule. Every sentence is functional, though the three quoted example questions are slightly redundant with the opening scope sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description fills the important gap by describing the return shape (per-state and per-year breakdown, site/closure info). Pagination limits are left to the schema, which documents them fully.

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 coverage is 100%, and the fuzzy-matching behavior ('Tesla' matches 'Tesla, Inc.' and 'TESLA MOTORS') is already documented in the company parameter. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource: retrieves every WARN Act layoff/closure notice for one employer across all covered states, plus a per-state and per-year breakdown. It explicitly contrasts with 'browsing a date range,' which separates it from the date-oriented siblings (warn_recent, warn_search) without needing to open their schemas.

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?

Usage is clearly framed: use it to trace one employer's layoff history, not to browse a date range. The when-not condition is stated in behavioral terms rather than by naming the sibling tool, which leaves a small inference step but is unambiguous about intent.

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.