WARN Firehose — Labor Market Intelligence

get_risk_signal

Get companies ranked by composite distress signal across all datasets.

Combines WARN layoff volume/recency, SEC restructuring filings,
bankruptcy filings, and H-1B denial rates into a single risk score.
Levels: Critical (7+), Elevated (4-6), Moderate (2-3), Low (1).
Requires Starter tier or higher. Get your API key at laborcurrent.com/account

Args:
    state: Optional 2-letter state code to filter
    min_score: Minimum risk score (default 3)
    limit: Max results (default 15, max 50)
    api_key: Your LaborCurrent API key (Starter tier required)

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the scoring thresholds, the data sources combined, and the authentication/tier requirement. The verb 'get' signals a read-only operation, though it doesn't explicitly state rate limits or absence of side effects; the output schema covers return shape.

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 front-loaded with purpose, then gives scoring levels, access requirements, and compact parameter bullets. It is longer than minimal but every section earns its place by conveying needed invocation details without fluff.

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?

Given the output schema exists, return-value documentation isn't needed. The description fully covers the composite score meaning, thresholds, data sources, access tier, and all four parameters, making it self-sufficient for an agent to invoke the tool correctly.

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?

Schema description coverage is 0%, so the Args section must compensate and does. It explains state as an optional 2-letter filter, min_score as a risk threshold, limit with max 50, and api_key with tier requirement. This meaningfully adds semantics beyond the raw schema fields.

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 opens with a specific verb and resource: 'Get companies ranked by composite distress signal across all datasets.' It then enumerates the exact data sources (WARN, SEC, bankruptcy, H-1B denial rates), which clearly differentiates it from sibling tools like get_company_layoffs or get_market_pulse that focus on narrower signals.

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 gives clear context: use this tool when you need a composite cross-dataset risk score, not a single-signal lookup. It doesn't explicitly name alternatives or exclusions, but the 'across all datasets' phrase and scoring-level explanation make the intended use obvious. It also discloses the Starter-tier requirement.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?