Skip to main content
Glama

get_workplace_safety_benchmark

Read-only

OSHA injury and illness rate benchmarks by company, industry, NAICS code, and state. Industry composite benchmarks available immediately with no sync required — establishment-specific data enabled when OSHA sync is connected. Covers injury rates, top-quartile performance, and EMR context for insurance, bonding, and public contract prequalification. $0.02 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": {
      "company_or_industry": "<company_or_industry>"
    },
    "name": "get_workplace_safety_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
naics_codeNo
company_or_industryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With readOnlyHint/openWorldHint already declaring the safety profile, the description adds useful behavior the annotations cannot: per-call pricing ($0.02 USDC) and a data-availability gate tied to OSHA sync state. It still says nothing about result shape, pagination, or what happens when a company has no establishment data.

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 tight sentences, front-loaded with the resource and its dimensions, then availability, then pricing. No filler, though the pricing sentence is a slight commercial non-sequitur relative to the retrieval guidance.

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?

For a three-parameter read-only lookup with no output schema, the description supplies enough to decide whether to call it and whether prerequisites are met. The remaining gap is operational detail on argument formatting and result content, which matters most at 0% schema coverage.

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%, so the description carries real weight, and it does name all three inputs (company, industry, NAICS code, state). However, it never explains the union parameter `company_or_industry` (what value to pass, ambiguity between a company name and an industry label) or expected formats for NAICS code and state, leaving the highest-risk parameter undocumented.

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 injury and illness rate benchmarks) and its exact slicing dimensions (company, industry, NAICS code, state), plus the metrics returned (injury rates, top-quartile performance, EMR). This is unmistakable against the sibling benchmark tools, which each cover a different domain.

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?

It gives concrete use contexts (insurance, bonding, public contract prequalification) and an explicit readiness condition: industry composites work immediately while establishment-specific data requires an OSHA sync. It stops short of stating when to prefer an alternative tool or when this tool is inappropriate.

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