Skip to main content
Glama
Sign In

X3 Compliance

by io.github.x3allamerican
OverviewDiscussionsAdmin

Is a hearing loss OSHA recordable (Standard Threshold Shift)?

osha_hearing_shift
Read-onlyIdempotent

Compare a baseline and current audiogram at 2000, 3000 and 4000 Hz under 29 CFR 1904.10: Standard Threshold Shift of 10 dB average plus a 25 dB hearing level in the same ear. Optional age correction from 29 CFR 1910.95 Appendix F.

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": {
      "baseline": "<baseline>",
      "current": "<current>"
    },
    "name": "osha_hearing_shift"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentYesSame shape as baseline
baselineYes{ age?, left: {2000, 3000, 4000}, right: {2000, 3000, 4000} } in dB
ageCorrectSexNoApply Appendix F age correction using the male or female table

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 establish that this is a read-only, idempotent, non-destructive, closed-world calculation. Beyond that, the description discloses the exact regulatory logic: a 10 dB average shift plus a 25 dB hearing level in the same ear, with optional age correction from Appendix F. It stops short of describing the return value or edge cases, but it adds substantive behavioral context for a calculation tool.

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?

Two dense sentences, front-loaded with the regulatory citation and the core calculation rule. Every phrase contributes to understanding the test, with no filler or repetition.

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 nested-object calculation tool with no output schema, the description supplies the regulatory basis and the threshold formula an agent needs to trust the tool. It could be stronger by stating what the tool returns (e.g., a recordable/not-recordable result) or how missing age data is handled, but it is largely complete for invocation.

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 100%: baseline format, current shape, and the ageCorrectSex enum are all documented. The description restates the frequencies and mentions the age-correction table, but adds little meaning beyond what the schema already provides for each parameter. Baseline 3 is appropriate when the schema carries the parameter 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 gives a specific verb (compare audiograms) and resource (baseline and current at 2000/3000/4000 Hz) tied to a precise regulatory test (29 CFR 1904.10 Standard Threshold Shift). The title and description together make it unmistakable that this tool handles hearing-loss recordability rather than general OSHA recordability.

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?

The description implies its use case (determining whether a hearing loss is an OSHA-recordable Standard Threshold Shift), but it never states when to choose this tool over alternatives like osha_is_recordable or what conditions make the calculation inapplicable. Usage is therefore inferable but not explicitly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All X3 Compliance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources