Skip to main content
Glama

Nlrb Recent Filings

nlrb_recent_filings
Read-onlyIdempotent

Newest US National Labor Relations Board case filings across the country over a recent window, the labor-dispute equivalent of a new-filings feed. Returns case number, name, date filed, status, city and region, newest first, with the total filed in the window. Answers "what NLRB charges were filed this week", "recent union election petitions", "how much labor board activity was there in the last 30 days". Filter by case type (C for unfair labor practice charges, R for election petitions) and NLRB region.

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": {
      "days": 7,
      "limit": 3
    },
    "name": "nlrb_recent_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back from today to include (1-365, default 7).
limitNoMax cases to return (1-50, default 25).
regionNoNLRB region number, e.g. "10", "29".
statusNoRestrict to "Open", "Closed", or "Open - Blocked".
case_typeNoRestrict to "C" (unfair labor practice charges) or "R" (representation/election petitions). Omit for both. "ULP" is accepted as a synonym for C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: results are newest-first, each record includes case number, name, date filed, status, city and region, and the response carries a total filed in the window. It does not discuss pagination limits or coverage latency, but the essentials are disclosed.

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 purpose and return shape are front-loaded in the first sentence, filters follow, and the example questions are compact and illustrative rather than filler. Slight redundancy between the return-field list and the example queries keeps it from being maximally tight.

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?

With no output schema, the description compensates by enumerating the returned fields and the aggregate total, and it explains the recency window and both filter dimensions. Combined with annotations covering safety and idempotency, an agent has everything needed to call this correctly without opening the schema.

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 description coverage is 100%, so all five parameters are already documented in the schema, including the C/R case_type codes, the 'ULP' synonym, and region examples. The description restates the case_type and region filters without adding syntax, ranges, or interaction rules beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 statement: 'Newest US National Labor Relations Board case filings across the country over a recent window,' and adds a useful analogy ('the labor-dispute equivalent of a new-filings feed'). It clearly implies a recency-scoped list rather than a single-case lookup, but it never names nlrb_case or nlrb_search, so sibling differentiation is left to inference.

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?

Three concrete example questions ('what NLRB charges were filed this week', 'recent union election petitions', 'how much labor board activity was there in the last 30 days') give a strong sense of the intended call contexts. It stops short of explicit when-not guidance or naming an alternative tool for historical or keyword-specific lookups.

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.