WARN Firehose — Labor Market Intelligence

get_state_intelligence

Get a unified state profile combining all 6 datasets for a US state.

Returns WARN notices, LCA petitions, H-1B approvals/denials, DOL claims,
bankruptcy matches, JOLTS data, and a composite distress score.
Requires Pro tier or higher. Get your API key at warnfirehose.com/account

Args:
    state_code: Two-letter state abbreviation (e.g. CA, TX, NY)
    api_key: Your WARN Firehose API key (Pro tier required)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No
`state_code`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that Pro tier is required and enumerates the returned data categories, which is useful. However, it does not mention rate limits, error handling, or behavior on invalid state codes, leaving some operational uncertainty for a first-time agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured. It front-loads the main purpose in the first sentence, then lists the return data, requirement, and parameters in a logical order. Every sentence contributes information without redundancy or fluff.

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?

The description covers the tool's scope, required access level, and return contents. Since an output schema exists, detailed return value documentation is available elsewhere. It could mention error handling, but for a data retrieval tool with a clear data list and access requirement, the description is sufficiently 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 provides no parameter descriptions (0% coverage), so the description must compensate. The Args section explains state_code as 'Two-letter state abbreviation' with examples, and api_key as the user's API key with a Pro tier note, adding meaning to both parameters. A minor ambiguity remains because api_key is optional in the schema but implied as necessary; still, the description significantly enhances schema semantics.

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: 'Get a unified state profile combining all 6 datasets for a US state.' It lists the specific datasets included, making it distinct from sibling tools like get_state_summary. The verb 'Get' and resource 'state profile' are specific and unambiguous.

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 states the Pro tier requirement and provides an API key link, giving clear context on prerequisites. However, it does not explicitly say when to use this tool versus alternatives like get_state_summary or get_market_pulse. Usage is implied by the 'unified state profile' phrase, but no exclusions or alternative recommendations are given.

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?