Skip to main content
Glama

Nlrb Case

nlrb_case
Read-onlyIdempotent

Full docket for one US National Labor Relations Board case by case number (e.g. "10-CB-393760", "31-RC-357638"): the allegations charged under the National Labor Relations Act (such as "8(a)(3) Discharge" or "8(b)(1)(A) Duty of Fair Representation"), status, date filed, location, assigned region, the participants (charged party, charging party, employer, union and their legal representatives), the docket activity log, and for representation cases the election tally, eligible voters, ballots counted, votes for and against the union. Answers "what is Starbucks charged with in this NLRB case", "how did the union election in case 31-RC-357638 turn out".

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": {
      "case_number": "10-CB-393760"
    },
    "name": "nlrb_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_numberYesNLRB case number in region-type-serial form, e.g. "10-CB-393760" or "31-rc-357638" (case-insensitive; surrounding whitespace ignored).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds substantive behavioral value beyond that by enumerating what the response contains: allegations charged, status, dates, region, participants with legal representatives, the docket activity log, and election tallies for representation cases.

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?

Front-loaded with the core action and key, followed by a dense enumeration of returned fields and then sample questions. It is a long single paragraph and the trailing quoted example questions are somewhat redundant, but nearly every clause carries useful information for a rich docket tool.

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?

With no output schema, the description carries the burden of explaining return content, and it does so thoroughly, including election-specific fields. It does not address error behavior for invalid or unknown case numbers, which is a minor remaining gap for a single-record lookup.

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% and the single case_number parameter already documents the region-type-serial format and case-insensitivity. The description reinforces the case-number key and supplies example values, but adds little syntax or constraint detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb and resource ('Full docket for one ... NLRB case') and pins the lookup key to a case number, with concrete examples like '10-CB-393760'. This is clearly distinguishable from nlrb_recent_filings (a feed) and nlrb_search (a query tool) without opening any schema.

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 makes the use context explicit by listing the questions it answers ('what is Starbucks charged with', 'how did the union election ... turn out'), which tells the agent this is a single-case detail lookup. It does not explicitly say when to prefer nlrb_search or nlrb_recent_filings instead, so no exclusion guidance is present.

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.