Skip to main content
Glama

Search the regulation corpus

search_law_corpus
Read-onlyIdempotent

Search the VERBATIM authority corpus behind Jobsite's training: 29 CFR regulation text (per-section, with citations), the CA/WA/OR state rules for heat illness and wildfire smoke, plus OSHA interpretations and NIOSH/CDC/EPA technical guidance the training cites. Use this when the user asks what an authority ACTUALLY SAYS — exact rule language, a specific citation ('what does 1926.501 require'), trigger heights, employer duties — and quote the returned text with its citation heading and jurisdiction. EVERY match carries an authority field: T1 is binding law, T2 is an agency interpretation and T3 is technical guidance. READ IT BEFORE YOU CHARACTERISE THE MATCH — quote a T2/T3 match as what that agency recommends or says, NEVER as what a regulation requires, and never call it a rule. It returns the source text itself, not a paraphrase of it — prefer it whenever the user wants what the rule says. The corpus spans the topics Jobsite trains on plus the authorities they cite, NOT all of 29 CFR: an empty result means 'not in the corpus', never 'no such rule exists'.

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": {
      "query": "<query>"
    },
    "name": "search_law_corpus"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax sections to return. Defaults to 4, cap 8.
queryYesPlain-words regulatory question or a citation number — 'fall protection trigger height', '1926.501', 'silica exposure control plan'.
jurisdictionNoOptional filter. Omit to search all jurisdictions (federal is most of the corpus).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world); the description goes well beyond by disclosing the T1/T2/T3 authority tiering, the instruction to read the tier before characterizing a match, and the crucial scope limit that the corpus is not all of 29 CFR. These are exactly the behavioral traits an agent could otherwise get wrong.

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?

Front-loads the corpus identity, then usage, then the tier-reading warning and scope caveat — good ordering. There is mild redundancy where 'it returns the source text itself, not a paraphrase' restates the earlier 'verbatim' framing and the 'prefer it whenever the user wants what the rule says' clause echoes the opening usage sentence.

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 no output schema, the description carries the return-value burden and does so: it explains that verbatim source text comes back with a citation heading, jurisdiction, and an `authority` field whose tiers it defines. Combined with the stated limit on the result count and corpus scope, an agent has everything needed to call and interpret it.

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 description coverage is 100%, so the baseline is 3. The description reinforces that queries can be plain phrasing or a citation number and that jurisdiction filters narrow to federal or a specific state, but it adds no syntax or format detail beyond what the schema already documents.

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 ('search the VERBATIM authority corpus') and enumerates the contents: 29 CFR section text, CA/WA/OR heat and wildfire smoke rules, OSHA interpretations, NIOSH/CDC/EPA guidance. This clearly separates it from siblings like search_articles and search_regulatory_news, which target different content types.

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 explicit when-to-use guidance ('when the user asks what an authority ACTUALLY SAYS — exact rule language, a specific citation') and clarifies empty-result meaning ('not in the corpus', never 'no such rule exists'). It does not name a sibling alternative for non-verbatim questions, so routing against search_articles is left implicit.

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