Skip to main content
Glama

OSHA Permissible Exposure Limits: chemical name, CAS

health_osha_occupational_health
Read-only

OSHA Permissible Exposure Limits (Table Z-1, 29 CFR 1910.1000, read from eCFR): chemical name, CAS number, 8-hour TWA in ppm and mg/m3, and notes such as ceiling or see-other-section. Matches by name words. Up to 20 chemicals per call; not the full OSHA chemical database. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "chemical": "<chemical>"
    },
    "name": "health_osha_occupational_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many chemicals, 1 to 20 (default 5)
chemicalYesChemical name words, letters, spaces, commas and hyphens, 3 to 60 characters

Output Schema

NameRequiredDescriptionDefault
asOfNo
queryNo
totalNo
sourceNo
checkedAtNo
chemicalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations it adds unique operational facts: the source of record (eCFR), name-word matching behavior, a 20-chemical ceiling, and a billing model with failed calls not charged. The gaps are minor — it doesn't describe result ordering or what happens when a name is ambiguous.

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?

One dense, semicolon-separated block that front-loads the dataset identity and provenance, then fields, matching, limits, and cost. No sentence is wasted, though the packed formatting makes the pricing detail easy to skim past.

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

Completeness5/5

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

With an output schema, annotations, and 100% parameter coverage already supplied, the description fills the remaining meaningful gaps: provenance, matching semantics, call ceiling, scope limitation, and price. An agent has everything needed to decide to call it and to budget for it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description earns an extra point by explaining that matching is name-word based rather than exact-string, which the schema's "Chemical name words..." hint only partially conveys. The 20-per-call limit reinforces the otherwise implicit meaning of the max parameter.

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 resource and provenance (OSHA PELs, Table Z-1, 29 CFR 1910.1000, read from eCFR) and enumerates the returned fields: chemical name, CAS, 8-hour TWA in ppm and mg/m3, and ceiling/see-other-section notes. An agent can distinguish this from a general chemical lookup like health_pubchem_chemical_cid without opening the 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?

"Matches by name words" plus "up to 20 chemicals per call; not the full OSHA chemical database" gives clear operating context and a scope exclusion. It does not name an alternative sibling for broader or identifier-based chemical lookup, so routing is inferable rather than explicit.

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