Skip to main content
Glama

get_osha_enforcement

Read-only

OSHA inspection and violation history for a named employer — total inspections, violations, cumulative penalties, and violation type breakdown. Source: DOL Enforcement Data. Use in vendor diligence, M&A, or ESG risk. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $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_osha_enforcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
employer_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the description's added value is provenance and cost: DOL Enforcement Data as source, a post-quantum signed receipt with a verification URL, and $0.10 USDC per call. That pricing and attestation detail is genuinely useful operational context an agent cannot get from structured fields, though it omits what happens on no-match or ambiguous employer names.

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?

Four short, front-loaded segments: what it returns, the source, the use cases, then attestation and price. Every clause carries information, though the attestation/verification sentence reads slightly promotional and could be compressed.

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 does the necessary work by enumerating the return fields (inspections, violations, penalties, type breakdown), and annotations cover safety. The remaining gaps are scope limits — no date-range or state filtering is mentioned despite the single-parameter schema — and penalty currency/temporal basis.

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 0% for the single employer_name parameter, and the description only says 'for a named employer' — it does not clarify whether an exact legal name is required, whether matching is fuzzy, or how subsidiaries are handled. It partially compensates by listing the aggregated outputs keyed to that name, but not the matching semantics.

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?

The description names a specific resource (OSHA inspection and violation history) scoped to a named employer, and enumerates the returned measures: total inspections, violations, cumulative penalties, and violation-type breakdown. The agency specificity (OSHA, DOL Enforcement Data) distinguishes it from agency-specific siblings like get_ftc_enforcement_history or get_occ_enforcement_actions without the reader needing to open a schema.

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?

It gives three concrete use contexts (vendor diligence, M&A, ESG risk), which implies when to reach for it, but never states when not to use it or names an alternative such as get_litigation_enforcement_snapshot for a multi-agency view. The agent must infer selection from the agency name alone.

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