Skip to main content
Glama
eutech-directory

Ligis-Link-mcp

generate_rams

Generate a formal safety document (RAMS/JHA/SWMS) for high-risk construction tasks, including hazard register, method steps, and required certifications. Compliant with regional safety regulations.

Instructions

[PRO] Generates a complete Risk Assessment and Method Statement (RAMS) document — called a Job Hazard Analysis (JHA) in the USA or Safe Work Method Statement (SWMS) in Australia. Use this tool when a foreman or PM needs a formal safety document before a high-risk task. Output includes: Section 1 — Hazard Register (tabular, with severity/likelihood/risk rating/controls/regulations), Section 2 — Method Statement (numbered sequential steps), Section 3 — Required Qualifications and Certifications. The document is formatted for printing or inclusion in a site safety file. This tool produces a longer output than other tools — expect 800-1500 words. Example tasks: 'Electrical switchboard installation in commercial building NSW', 'Gas line installation in residential kitchen UK', 'Roof framing timber frame residential NSW'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tradeYesThe trade performing the work.
regionYesJurisdiction. Determines applicable WHS/CDM/OSHA legislation cited in the document.
taskYesFull description of the task requiring the RAMS. Include: what work, where, at what height or voltage, any confined space, any hot work. The more detail, the more accurate the hazard register.
company_nameNoOptional. Company name to include in the document header.
site_addressNoOptional. Site address to include in the document header.
roleNoRole of the person generating the RAMS. Foreman or PM recommended.Foreman
api_keyNoPro API key required.
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the output is 800-1500 words and mentions it is a PRO tool, but does not address mutation, auth requirements beyond the api_key parameter, or any side effects. Adequate but not robust.

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?

The description is four sentences, front-loads purpose, then usage, output structure, and examples. Every sentence adds value with no redundancy.

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?

Despite no output schema, the description explains the three-section output format, formatting for printing, and expected word count. It covers the tool's purpose, usage, output structure, and provides examples, making it complete for the tool's complexity.

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?

Input schema covers all 7 parameters with descriptions (100% coverage). Description adds marginal value, noting that more detail in the task parameter improves accuracy, but does not elaborate on parameter semantics beyond the schema.

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 clearly states the tool generates a complete RAMS/JHA/SWMS document, lists specific sections (Hazard Register, Method Statement, Qualifications), and provides examples, distinguishing it from siblings like generate_safety_checklist which are lighter.

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?

Explicitly says to use 'when a foreman or PM needs a formal safety document before a high-risk task,' providing strong contextual guidance. Lacks explicit when-not or alternative naming but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eutech-directory/legis-link-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server