Skip to main content
Glama

Stratalize Intelligence

Get Workplace Safety Benchmark

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. 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 (read-only, open-world, non-destructive), and the description adds genuinely non-obvious behavior: the sync dependency gate for establishment-level data and a per-call price of $0.02 USDC. It still omits what a response looks like structurally and what happens if the OSHA sync is missing at call time.

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 sentences, front-loaded with the resource definition, then availability constraints, then use cases and price. Dense with little waste, though the use-case list is a slightly sprawling clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, gating, and cost, which is more than most benchmark tools, but with no output schema and zero schema description coverage the agent still lacks return-shape expectations and the interaction rules among the three optional/required parameters. Adequate but with visible gaps for a paid, sync-dependent data tool.

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 parameter meaning. It does clarify that company_or_industry accepts either a company or an industry and that NAICS code and state are additional slicing keys, but it gives no format guidance (e.g. NAICS digit length) and does not explain how the three parameters combine or what the single-value default is.

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 injury and illness rate benchmarks — plus the exact dimensions (company, industry, NAICS, state) it slices on. It is unambiguously the workplace-safety member of the benchmark family, so an agent can separate it from siblings like get_esg_benchmark or get_bank_regulatory_benchmark without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage contexts (insurance, bonding, public contract prequalification) and a key operational distinction: industry composites work immediately with no sync, while establishment-specific data requires an OSHA connection. It does not name an alternative tool or state explicit exclusions, so it stops short of full when/when-not 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