WARN Firehose — Labor Market Intelligence

export_records

Export WARN records in bulk. Requires Pro tier or higher.

Returns up to 500 records with full field details. For CSV/Parquet
downloads, use the REST API at /api/export/.
Get your API key at warnfirehose.com/account

Args:
    api_key: Your WARN Firehose API key (Pro tier required)
    state: Optional 2-letter state code filter
    company: Optional company name filter (partial match)
    days: Look back this many days (default 90, max 730)
    limit: Max records to return (default 100, max 500)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`limit`	No
`state`	No
`api_key`	Yes
`company`	No

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key behavioral details: requires Pro tier, returns up to 500 records, includes full field details, and specifies parameter defaults (days=90, limit=100) and maximums (days max 730, limit max 500). It also mentions the API key requirement. This goes beyond minimal transparency, though it doesn't detail error handling or response format beyond 'full field details.'

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?

The description is well-structured, front-loading the purpose, then requirements, behavior, alternative method, and an organized Args list. It includes a redundant mention of the API key in two places and a URL that could be trimmed, but overall every sentence serves a purpose and the format is clear.

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 no annotations, no output schema, and simple parameters, the description covers purpose, all parameters, limits, auth requirements, and an alternative download path. It states return details ('up to 500 records with full field details') but doesn't enumerate fields or describe error cases. For a straightforward export tool, this is largely complete, though slightly more detail on response structure would elevate it.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must explain all parameters. It does so thoroughly: api_key (purpose and tier), state (2-letter filter), company (partial match), days (lookback with default/max), and limit (max records). This adds significant meaning beyond the bare schema property names and types, fully compensating for the lack of schema descriptions.

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 clearly states the tool's function: 'Export WARN records in bulk.' The verb 'export' and resource 'WARN records' are specific, and the bulk nature distinguishes it from tools like search_layoffs or get_recent_layoffs. The purpose is unambiguous and well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for bulk exports and notes an alternative for CSV/Parquet downloads via the REST API, but it does not explicitly contrast this tool with sibling tools. It mentions the Pro tier requirement, but lacks direct guidance on when to choose this over search_layoffs or get_state_summary. The REST API alternative is useful but not a sibling-tool comparison.

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

All WARN Firehose — Labor Market Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation3/5

Several tools overlap in function: get_recent_layoffs, get_state_summary, and search_layoffs all return layoff notices with various filters. get_state_intelligence also overlaps with get_state_summary but adds cross-dataset information. Descriptions help, but an agent may struggle to choose the right tool without careful reading.

Naming Consistency4/5

Most tools follow a get_verb pattern and use snake_case consistently. A few deviations like authenticate (verb-only), search_layoffs, and export_records are action-oriented but acceptable, making the overall pattern mostly predictable.

Tool Count5/5

With 12 tools, the server is well-scoped for a labor market intelligence API. Each tool serves a distinct purpose, and the count is neither sparse nor overwhelming for the domain.

Completeness4/5

The tool set covers core workflows: authentication, search, bulk export, state-level intelligence, risk signals, and talent pipeline. Minor gaps exist, such as no company-level cross-dataset view (similar to state_intelligence for a company) and no direct record-by-ID retrieval, but these are workable.

Resources

Need Help?