Skip to main content
Glama

Stratalize Intelligence

Get Osha Enforcement

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. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely non-obvious context: the upstream source (DOL Enforcement Data) and the $0.10 USDC per-call cost, which materially affects invocation decisions. The cryptographic attestation and verification URL sentences are provenance claims rather than behavior an agent needs to call the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and payload are front-loaded and waste-free, but roughly a third of the text is attestation and verification boilerplate that does not help an agent decide to call the tool. The cost note earns its place; the post-quantum receipt and verify URL do not.

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 usefully summarizes the return shape, and for a one-parameter read-only lookup it covers what an agent needs. The residual gap is input behavior — name-matching rules and empty-result handling — which is not addressed.

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 0%, so the description must carry the parameter meaning, and it only partially does: 'for a named employer' signals that the single parameter is an employer identity. It does not say whether matching is exact or fuzzy, whether legal name vs DBA/ticker works, or what happens with ambiguous or no-match names.

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 — OSHA inspection and violation history for a named employer — and enumerates the payload (total inspections, violations, cumulative penalties, violation type breakdown). The agency scoping (OSHA, source DOL Enforcement Data) makes it cleanly distinguishable from siblings such as get_ftc_enforcement_history and get_occ_enforcement_actions.

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 concrete use contexts (vendor diligence, M&A, ESG risk), which is more than most sibling definitions offer. It stops short of stating when NOT to use it or naming an alternative when the question is cross-agency or entity-wide rather than OSHA-specific.

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