Skip to main content
Glama

get_dol_labor_violations

Read-only

Use when screening an employer, vendor, or acquisition target for wage and hour compliance risk before a contract award, supply chain partnership, PE acquisition, or HR due diligence review. Returns DOL Wage and Hour Division enforcement history — FLSA overtime violations, minimum wage violations, child labor violations — with back wages assessed and employees affected. Repeat violations are a strong predictor of class action exposure. Example: Logistics Co LLC — 3 WHD investigations 2019-2023, $1.2M back wages, 891 employees affected for FLSA overtime violations — classified repeat violator, 340% higher class action probability vs first-time violators. Source: DOL WHISARD Enforcement Database. $0.10 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "employer_name": "<employer_name>"
    },
    "name": "get_dol_labor_violations"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
employer_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only/safe semantics, but the description adds real value beyond them: the exact source system (DOL WHISARD Enforcement Database), the contents of the response (back wages, employees affected, violation types), and the $0.10 USDC per-call cost. It does not describe latency, coverage period limits, or how employers are matched.

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 'Use when' trigger and tight throughout; the worked example and cost line are justified given the specificity they add. Slightly long, but each sentence carries information.

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?

No output schema exists, and the description sketches the return payload (investigation counts, back wages, employees affected, repeat-violator classification) along with source and cost. Only the input-side semantics — especially the optional state filter — remain unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters. The description implies the tool takes an employer name but says nothing about matching rules (legal name vs. DBA, exactness) or what the optional state parameter does. With low coverage, the description should have compensated and does not.

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 (returns DOL Wage and Hour Division enforcement history) plus the decision it supports (screening an employer/vendor/acquisition target for wage and hour compliance risk). Clearly distinguishable from the benchmark-oriented siblings in the catalog.

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?

Explicitly names the triggering situations — contract award, supply chain partnership, PE acquisition, HR due diligence. It gives no when-not guidance and names no alternative tool, so it stops short of full routing guidance.

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.

Resources