Skip to main content
Glama

Check compliance

check_compliance
Read-onlyIdempotent

Answers construction trade compliance questions with exact code references and clause citations. Use this tool when a tradesperson or engineer asks whether a specific installation, practice, or configuration is compliant with local regulations. Returns a COMPLIANT, NON_COMPLIANT, or REQUIRES_VERIFICATION status with the precise standard (e.g. AS/NZS 3000:2018 Clause 3.2.4) and any critical caveats. Covers electrical, plumbing, HVAC, welding, carpentry, roofing, gas fitting, solar, fire protection, and concrete trades across Australia, UK, USA, Canada, and EU. Do NOT use this tool for numerical calculations (use calculate_technical_spec instead) or for generating safety checklists or RAMS documents.

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": {
      "trade": "<trade>",
      "region": "<region>",
      "question": "<question>"
    },
    "name": "check_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoThe role of the person asking. Affects the depth and terminology of the answer.Qualified Tradesperson
tradeYesThe construction trade relevant to the question. Must match a supported trade exactly.
regionYesUse the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction for the compliance check. Examples: 'NSW', 'England', 'Texas', 'Ontario', 'Germany'. Determines which standard applies.
api_keyNoLegis-Link API key. Optional: leave empty for the free tier (a daily question limit applies); Pro users paste their ll_p_ key. Get a free key at https://legis-link.com
questionYesThe compliance question in plain English. Be specific: include voltages, distances, materials, or load values where relevant. Example: 'Is 2.5mm2 TPS cable compliant for a 20A circuit in a wall cavity?'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Legis-Link API key. Optional: leave empty for the free tier (50 requests/day); Pro users paste their ll_p_ key. Get a free key at https://legis-link.com"New value: +"Legis-Link API key. Optional: leave empty for the free tier (a daily question limit applies); Pro users paste their ll_p_ key. Get a free key at https://legis-link.com"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read; the description goes well beyond that by disclosing the response shape (three statuses, precise standard plus caveats), the jurisdiction-specific standard selection, and the trade/region coverage. Since there is no output schema, this return-value disclosure is exactly the burden the description needed to carry.

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-loaded with purpose and usage, then exclusions, with no filler sentences. Minor deduction because the lengthy trade list ("electrical, plumbing, HVAC, welding...") duplicates the trade enum already present in the schema and could have been compressed.

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?

No output schema exists, yet the description tells the agent what comes back and at what specificity. Combined with a fully documented 5-parameter schema and annotations covering safety profile, an agent has everything needed to decide and call correctly.

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% and the schema already explains the role-dependent answer depth, trade enum matching, the strong region guidance ("never assume NSW or Australia"), and the api_key free-tier/Pro distinction. The description adds essentially no parameter-level detail beyond restating which trades and regions exist, so the baseline 3 applies.

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 opens with a specific verb+resource ("Answers construction trade compliance questions with exact code references and clause citations") and names the exclusions (calculate_technical_spec, safety checklists/RAMS) so the agent can separate it from adjacent tools. The stated output vocabulary (COMPLIANT / NON_COMPLIANT / REQUIRES_VERIFICATION) further pins down what this tool is versus a generic code lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("when a tradesperson or engineer asks whether a specific installation, practice, or configuration is compliant") plus explicit when-not-to-use for numeric calculations and document generation, with the alternative tool named in each case. The remaining ambiguity, versus get_code_reference, is the only small gap.

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.