Skip to main content
Glama
Sign In

SDSentry: Safety Data Sheet Lookup, GHS Pictograms & HazCom

by com.0xpi.sdsentry
OverviewDiscussionsAdmin

Find a safety data sheet (SDS) for a chemical or product

find_safety_data_sheet
Read-onlyIdempotent

Look up the safety data sheet (SDS/MSDS) for a workplace chemical or product by name. Returns the product name, manufacturer, CAS number(s), EPA registration where applicable, a link to the actual SDS PDF, whether that PDF is manufacturer-hosted or a third-party copy, the revision date printed on it, the signal word and GHS pictograms when they could be read from the sheet, and a confidence level. For a sheet it finds it also returns two links: SDSentry's free, no-signup printable GHS secondary-container label maker for that product (it fills the label from the sheet when the sheet's Section 1 is confirmed and its label elements were read; otherwise the hazard classes are ticked by hand), useful when someone needs to label a spray bottle, jug or other workplace container; and the public result page showing the host and revision date, plus the pictograms and Section 1 check when the sheet has been read. If the product cannot be identified reliably it says so plainly rather than guessing — a wrong SDS is worse than none. With language "es" it also returns the manufacturer's own Spanish SDS link when SDSentry has found and read one (its Spanish Section 1 names the same product and maker; never a machine translation), says plainly when none was found or the sheet has not been checked yet, and gives the label's signal word, pictogram names and hazard statements in the official UN GHS Spanish wording for each code, with the label link pointing at the Spanish label maker. Free, no signup. Use it when someone needs hazard or handling information, or the SDS, for a chemical they keep on site.

Input Schema

NameRequiredDescriptionDefault
productYesThe chemical or product name to look up (at least 2 characters).
languageNoOptional output language. "es" adds the manufacturer's own Spanish SDS link when one was found and read, and the label elements in the official UN GHS Spanish wording. Default "en".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional output language. \"es\" adds the manufacturer's own Spanish SDS link when one was found and read, and the label elements in the official UN GHS Spanish wording. Default \"en\".",
+  "enum": [
+    "en",
+    "es"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, so the safety profile is covered; beyond that the description adds genuine behavior: a confidence level, an explicit refusal to guess when the product can't be identified, disclosure of whether the linked PDF is manufacturer-hosted or a third-party copy, and what happens with language=es (never a machine translation, says plainly when none found or unchecked). That is substantive context an agent could not infer.

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

Conciseness2/5

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

One enormous run-on paragraph of roughly 250 words, with several very long sentences whose clauses nest (the label-maker sentence alone carries multiple parenthetical conditionals). The core purpose is front-loaded, but the label-maker and result-page plumbing occupy far more space than an agent needs to select and call the tool.

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?

With no output schema, the description carries the return-value burden and does it thoroughly: field list, link types, confidence level, and the failure mode of not guessing. Complete enough to call correctly; only the sibling-selection guidance is missing.

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 100%, so both parameters are already documented; the description nonetheless adds meaning to language=es by spelling out the concrete consequences (manufacturer's own Spanish SDS link, official UN GHS Spanish wording for signal word, pictogram names and hazard statements, Spanish label link). The product parameter gets no extra semantics beyond the schema.

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?

States a specific verb and resource: look up an SDS/MSDS for a workplace chemical or product by name, and enumerates what comes back (product name, manufacturer, CAS, EPA reg, PDF link, revision date, signal word, pictograms, confidence). It never names or distinguishes itself from the obvious siblings search_sds and find_sds_for_inventory, so an agent cannot tell from the text which lookup to pick.

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 closing sentence gives a use case (hazard or handling information, or the SDS, for a chemical kept on site) and the language branch hints at a second use, but there are no exclusions and no named alternatives despite two near-identical siblings. Usage is implied rather than routed.

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

All SDSentry: Safety Data Sheet Lookup, GHS Pictograms & HazCom 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