Skip to main content
Glama

Whd Search

whd_search
Read-onlyIdempotent

Search concluded US Department of Labor Wage & Hour Division enforcement cases since FY2005, wage theft, back wages, minimum wage and overtime violations, child labour, H-1B and H-2A findings. Filter by employer name, NAICS industry code, or state. Returns the employer, industry, violation count, employees due back wages, civil money penalties and the findings dates for each case. Use for "has been cited for wage violations".

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": {
      "employer": "Walmart"
    },
    "name": "whd_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCases to return, 1-100 (default 20).
naicsNoNAICS industry code as stored by WHD (e.g. "09310").
sinceNoOnly cases whose findings END on or after this date (YYYY-MM-DD).
stateNoTwo-letter state code, e.g. "TX".
_apiKeyNoOptional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
employerNoEmployer name, matched as a substring against both the trade name and the legal name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds real context beyond them: the corpus is limited to *concluded* cases since FY2005 and it enumerates the returned fields (employer, industry, violation count, employees due back wages, penalties, findings dates). It does not describe pagination, sort order, or what an empty result means, which would have pushed it higher.

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 sentences, front-loaded with scope, then filters, then return shape, then usage trigger — each carries information. Slightly dense with keyword stuffing ('wage theft, back wages, minimum wage and overtime violations, child labour, H-1B and H-2A findings') but no sentence is redundant.

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?

There is no output schema, so the description usefully names the returned fields, and it covers corpus scope, filters and a usage example for a zero-required-parameter tool. Remaining gaps are operational details (result ordering, pagination beyond limit, whether the API key changes rate limits) that are minor for a read-only search.

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 the schema already documents limit, naics, since, state, employer and the API key, including the substring matching behavior. The description's parameter sentence largely restates the schema's filterable fields and adds no new semantics, so the baseline 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?

States a specific verb and resource: 'Search concluded US Department of Labor Wage & Hour Division enforcement cases since FY2005', enumerates the violation types covered and the filterable dimensions (employer, NAICS, state). An agent knows exactly what corpus is being queried, though it does not explicitly contrast itself with siblings like whd_employer or whd_top_backwages.

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?

Gives a concrete use-case trigger in the form of a user question ('has <employer> been cited for wage violations'), which is actionable guidance for when to reach for this tool. It stops short of stating when NOT to use it or naming a sibling as the alternative for aggregate/lookup queries.

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.