WARN Firehose — Labor Market Intelligence

get_talent_pipeline

Find available talent from recent layoffs, cross-referenced with LCA visa roles.

Shows what occupations/skills each laid-off company was hiring for.
Useful for recruiters targeting skilled workers from recently laid-off companies.
Requires Starter tier or higher. Get your API key at warnfirehose.com/account

Args:
    state: Optional 2-letter state code
    days: Look back this many days (default 90)
    limit: Max results (default 15, max 50)
    api_key: Your WARN Firehose API key (Starter tier required)

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.1/5.0

Behavior3/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 the API key requirement and Starter tier, which is helpful for authentication. However, it does not mention rate limits, read-only nature, or error behavior, leaving some transparency gaps.

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 efficiently structured with an intro, use case, requirement, and args block. Each sentence earns its place, though the API key URL could be considered slightly verbose. Overall, it is concise and well-organized.

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?

Given the presence of an output schema and 4 parameters, the description covers purpose, usage, authentication, and parameters. It does not explain return values, but the output schema likely does. Minor gap: no explanation of what 'cross-referenced with LCA visa roles' means operationally, but overall complete.

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

Parameters4/5

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

The schema has minimal descriptions (0% coverage), but the description's Args section explains each parameter: state as a 2-letter code, days as lookback, limit with max 50, and api_key with tier requirement. This adds meaning beyond the schema's default values and types.

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 purpose: 'Find available talent from recent layoffs, cross-referenced with LCA visa roles' and explains it shows 'what occupations/skills each laid-off company was hiring for.' This specific verb+resource combination distinguishes it from siblings like get_recent_layoffs or get_company_layoffs.

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?

The description provides clear usage context: 'Useful for recruiters targeting skilled workers from recently laid-off companies.' It does not explicitly mention alternatives or when-not-to-use, but the use case is specific enough to guide selection.

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?