Skip to main content
Glama

NS Pros MCP Gateway

nlrb__nlrb_search

Search US National Labor Relations Board cases by employer, union, or case number, unfair labor practice charges (C cases: CA against an employer, CB against a union) and union representation/election petitions (R cases: RC, RD, RM). Returns case number, case name, date filed, open/closed status, city and NLRB region for each match, plus the total number of matching cases. Answers "is Starbucks facing an NLRB charge", "labor board complaints against Amazon", "union election petitions at Trader J

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": {
      "limit": 3,
      "query": "Starbucks Corporation"
    },
    "name": "nlrb__nlrb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page of results, for paging past the first `limit` cases.
sortNo"newest" (default), "oldest", or "relevance".
limitNoMax cases to return (1-50, default 10).
queryYesEmployer name, union name, or a full case number such as "10-CB-393760". Matched full-text against case names; case-insensitive.
regionNoNLRB region number, e.g. "10" (Atlanta), "29" (Brooklyn). Two digits; single digits are zero-padded.
statusNoRestrict to "Open", "Closed", or "Open - Blocked".
case_typeNoRestrict to "C" (unfair labor practice charges) or "R" (representation/election petitions). Omit for both.
filed_sinceNoOnly cases filed on or after this date (YYYY-MM-DD).
filed_beforeNoOnly cases filed on or before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 behavioral burden; it does disclose the returned field set (case number, name, date filed, open/closed status, city, region) and that a total match count is included, which is valuable given there is no output schema. It says nothing about auth, rate limits, match-ordering, or how ambiguous multi-match queries behave.

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?

Three dense sentences: capability and taxonomy first, return shape second, example questions last. Front-loaded and mostly waste-free, though the quoted example questions are illustrative rather than operational and could be trimmed.

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?

For a nine-parameter, unannotated tool with no output schema, the description covers purpose, result shape, and match count well. Remaining gaps are minor: paging interaction with limit, default sort behavior, and whether unions are matched separately from employer names are left to 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 coverage is 100%, so all nine parameters are already documented, including the case-number format example and the region zero-padding rule. The description adds domain color (CA charges against employers vs CB charges against unions; RC/RD/RM petitions) but does not map that back to the case_type or query parameters in a way the schema doesn't already convey.

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?

States a specific verb and resource ('Search US National Labor Relations Board cases') and scopes it to employer, union, or case number, then explains the C/R case taxonomy. The scope makes it inferable how this differs from nlrb_case or nlrb_recent_filings, but no sibling is named, so 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 Guidelines3/5

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

No explicit when-to-use or when-not guidance, and no named alternatives. Usage is only implied by the sample questions ('is Starbucks facing an NLRB charge'), which suggest entity-centric lookup rather than single-case retrieval or recent-filing monitoring.

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.