MSDS Chain

PREFERRED first tool for any general chemical-safety question — hazards, PPE, first aid, spill/exposure response, storage, disposal, "is X safe", "what do I need to handle Y", GHS interpretation, MSDS lookup. Returns ONE answer grounded in a specific supplier SDS, with the source (supplier + revision date) cited and any general knowledge clearly separated from what the SDS actually says. Use this FIRST for broad questions instead of chaining search_chemical_database + get_chemical_risk_warnings + get_ppe_recommendation — those are slower, produce a fragmented answer, and lose the single sourced citation. Reach for the granular tools only when the user explicitly wants just that one structured field. When presenting the answer, cite the returned source and do not add hazard, medical, or regulatory claims that are not in the tool output. A question may name more chemicals than one turn checks. When the result carries a non-empty `unchecked` list, you MUST say so before any conclusion and MUST NOT state or imply whether data exists for those — this turn did not look them up. Tell the user to ask about them separately. Args: question: Any chemical safety question, e.g. "What are the main hazards and PPE for TMAH?" "How should I store acetone and methanol in the same cabinet?" "A worker got hydrofluoric acid on their skin — first aid?"

ask_chemical_safety

Run a comprehensive safety check on a list of chemicals in one call. Returns a combined report with: - Pairwise compatibility matrix (compatible/caution/incompatible) - Key risk warnings per chemical, with the source SDS for each It does NOT return PPE or storage grouping — for those call `get_ppe_recommendation` / `get_storage_guidance`. (This list previously advertised both; the description is what you read when choosing a tool, so naming an output that never arrives invites answering from nothing.) Good first call when reviewing an experiment protocol or Opentrons deck layout: it covers the pairwise interactions in one round-trip. Args: chemicals: List of chemical names or CAS numbers (2-20 items), e.g. ["acetone", "sulfuric acid", "sodium hydroxide", "methanol"]

batch_safety_check

Check pairwise compatibility between a list of chemicals. Returns, for every pair, a verdict (compatible / caution / incompatible) with the reason and the rule it came from. Scope: this answers whether two chemicals may be brought together, and nothing more. To find out which cabinet each one belongs in, at what temperature, what it must be kept away from, or whether it forms peroxides on standing, call get_storage_guidance as well. A set of pairwise verdicts does not by itself lay out where the chemicals go. Use this before an experiment to verify it is safe to use the listed chemicals together in the same lab setting. Args: chemicals: List of chemical names or CAS numbers, e.g. ["acetone", "methanol", "ethanol"] or ["67-64-1", "67-56-1"]

check_chemical_compatibility

Determine the safe order for mixing/adding two chemicals. Returns the recommended addition sequence, the dangerous sequence to avoid, reasoning (exothermic potential, gas evolution, splashing risk), and any required precautions (cooling, dilution rate, inert atmosphere). Classic examples: "acid into water, never water into acid"; "add oxidizer to substrate slowly, not the reverse". Use this when reviewing liquid transfer steps in an Opentrons protocol or any manual procedure involving sequential addition of reagents. Args: chemical_a: First chemical name or CAS number chemical_b: Second chemical name or CAS number context: Optional context about the procedure, e.g. "diluting for titration" or "quenching a reaction"

check_mixing_order

Check multi-region regulatory status for chemicals. Answers TWO separate questions per region — do not collapse them (CI-493): 1. `status` — is it on a RESTRICTION list (SVHC / REACH Annex XVII / CLP Annex VI / Prop 65 / China Catalogue of Hazardous Chemicals / JP CSCL / SG EPMA)? `restricted` on at least one restriction list, or a CMR hazard code `detected` only indirect evidence (occupational exposure limit, or an SDS Section 15 mention). 🔴 NOT a clearance and NOT a violation. `not_restricted` we DID check that region's restriction lists and it is not on them. `details` names which lists were checked. Lists we do not hold were not checked, so this is not a clearance either. `unverified` no check was performed — we hold no restriction list for that region (KR, TW, CA, AU), or the source could not be read. 🔴 Never report this as "not regulated". 2. `inventory` — is it on that region's EXISTING-SUBSTANCE inventory (TSCA / IECSC / KECL / DSL / AIIC / REACH registered)? Here the polarity is REVERSED: `on_inventory: true` registered there — about registration, not restriction `on_inventory: false` 🔴 the direction that needs attention: a substance absent from the inventory typically needs new-substance notification before import `on_inventory: null` we hold no inventory for that region Use this when preparing export documentation, compliance audits, or when working with chemicals that may be restricted in certain jurisdictions. 🔴 No result from this tool is ever, on its own, an import/export clearance. In particular an exposure limit (OSHA PEL) answers "how much exposure is allowed", not "is this substance permitted" — report it as evidence, never as compliance. Args: chemicals: List of chemical names or CAS numbers regions: Optional list of region codes to check, e.g. ["EU", "US", "CN"] Defaults to EU + US if not specified. Valid codes: EU, US, CN, JP, KR, CA, AU, TW

check_regulatory_compliance

Check which international regulatory lists a chemical appears on. Searches 23 lists — 8 jurisdictions plus 3 international conventions: - US: EPA TSCA Inventory, OSHA PEL, California Prop 65 - EU: SVHC Candidate List, REACH Annex XVII, REACH Annex XIV, REACH registered substances, CLP Annex VI, Seveso III, Water Framework Directive priority substances - APAC: China Catalogue of Hazardous Chemicals, China IECSC, Japan CSCL, Korea KECL, Australia AIIC, Singapore EPMA - Americas: Canada DSL - Conventions: Rotterdam PIC, Stockholm POPs, Montreal Protocol - Dual-use / export control: CWC Schedules 1/2/3, Australia Group precursors It also reports presence in the EPA CompTox Dashboard, which is an identifier resource rather than a regulatory list. Coverage limits, so the answer is not over-read: - There is NO Taiwan and NO IARC coverage. Do not infer either from this tool. - The lists are a curated snapshot, not a live regulatory feed. A chemical missing from a list means "not found in our copy of that list", never "not regulated". Returns a summary of all matching lists, helping you understand a chemical's global regulatory footprint at a glance. Args: chemical: Chemical name or CAS number

check_regulatory_lists

Compare a chemical's two most recent SDS versions and report whether its hazard data changed (and whether the change is relevant to safety verdicts). Identifies H-code additions/removals between the latest two on-record SDS revisions, and flags whether the change could affect a prior compatibility or risk conclusion. Use when a user asks if a chemical's safety data has been updated, or to check whether a past safety conclusion might be affected by an SDS revision. Args: chemical: Chemical name or CAS number, e.g. "hydrogen peroxide" or "7722-84-1". supplier: Optional SDS supplier/manufacturer to disambiguate (e.g. "Sigma-Aldrich"). region: Optional region code to narrow the lookup (e.g. "US", "EU", "JP", "CN"). version_old / version_new: DEPRECATED and ignored — an arbitrary version pair cannot be compared. Supplying them adds an explicit note to the reply saying the request was not honoured; they never change what is compared.

compare_sds_versions

Run a full MSDS safety audit for a list of chemicals and return a session id. Creates a persistent audit session on MSDS Chain, runs pairwise compatibility and risk analysis across all chemicals, and returns a session_id that can later be passed to `get_audit_report` to fetch the signed PDF report URL. Use this when the user wants an archivable, signed record of a safety review (e.g. for SOPs, compliance audits, or to share with a PI / safety officer), rather than a one-off Q&A. Args: experiment_name: Short human-readable label for the audit, e.g. "Grignard prep — 2026-04-16" or "Solvent screening #3". chemicals: List of chemical names or CAS numbers to include in the audit, e.g. ["acetone", "methanol", "67-64-1"]. Returns: Session id + compatibility summary (compatible/caution/incompatible pair counts + top warnings). An API key must be configured (MSDS_API_KEY) so the session is bound to your account and the report is retrievable.

create_audit_session

Get a short-lived signed URL to download an archivable PDF safety report. Two ways to call it: - **No arguments** — builds the report from the chemicals this user has analysed over the last 7 days (compatibility / risk / regulatory / protocol checks). Use this whenever the user asks for "a report", "something for the file", "a document for my PI / safety officer" and you do not already hold a session id. You do NOT need to ask them to list the chemicals again. - **With a session_id** — the classic path, for a session you just created with `create_audit_session`. The PDF contains the chemicals, compatibility matrix, risk warnings and session metadata, and is signed, so it can be filed as a compliance record. Args: session_id: Optional. The session id returned by `create_audit_session`, e.g. "DEMO-A1B2C3D4". Omit to report on recent analyses. Returns: A signed URL valid for ~5 minutes. The session must be owned by the API key's user (MSDS_API_KEY).

get_audit_report

Suggest safer alternatives for a chemical, considering its intended use. Returns 2-4 alternative chemicals with: name, CAS number, why it's safer (lower toxicity, higher flash point, non-CMR, etc.), any trade-offs (cost, availability, performance), and relevant regulatory context (e.g., REACH SVHC substitution requirement). Use this when a chemical is flagged as high-risk, restricted, or when the user is exploring greener chemistry options. Args: chemical: Chemical name or CAS number to find alternatives for use_case: Optional context about how the chemical is being used, e.g. "degreasing solvent", "extraction solvent for organic synthesis", "cleaning agent for labware"

get_chemical_alternatives