Skip to main content
Glama

Who enforces workplace safety in a state (OSHA State Plans)

osha_state_jurisdiction
Read-onlyIdempotent

For a state and employer type (private, state-local, federal), say whether federal OSHA or a State Plan (like MIOSHA or Cal/OSHA) has jurisdiction, with the plan's agency, website and 29 CFR 1952 citation.

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": {
      "state": "<state>",
      "employer": "<employer>"
    },
    "name": "osha_state_jurisdiction"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState name or two-letter code
employerYesprivate, state-local or federal

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds that the answer resolves to either federal OSHA or a named State Plan agency and includes a 29 CFR 1952 citation, but it does not say how states without a plan, territories, or partial-coverage plans are reported.

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

Conciseness5/5

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

A single sentence that front-loads the input contract (state + employer type) and then the payoff (jurisdiction plus agency, website, citation). No filler, no restatement of the title.

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 enumerates the return contents (agency, website, 29 CFR 1952 citation) and covers both possible outcomes, which is the key thing an agent needs. It falls short only on edge cases — states with no plan, territories, or public-sector-only coverage — which a jurisdiction tool could reasonably encounter.

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 enum for employer is already documented in the schema, so the schema does the heavy lifting. The description adds only the gloss 'private, state-local, federal' and no guidance on how state inputs are normalized (name vs. two-letter code) or what happens with invalid values — baseline 3 is appropriate.

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?

The description names a specific resource (jurisdiction over workplace safety by state) and a concrete verb output ('say whether federal OSHA or a State Plan ... has jurisdiction'), with parenthetical examples (MIOSHA, Cal/OSHA) that anchor the concept. It does not explicitly differentiate itself from siblings such as osha_coverage, though the jurisdiction framing is distinct enough that an agent can place it.

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?

Usage is implied rather than stated: an agent can infer this is the tool for 'who enforces here' questions, but there is no explicit when-to-use, no prerequisites, and no statement of boundary against adjacent tools like osha_coverage. The employer-type dimension hints at the scoping question it answers, which keeps it above 'no 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.