Skip to main content
Glama
eutech-directory

Ligis-Link-mcp

verify_material_compliance

Check if a material meets code requirements for your trade and jurisdiction. Get compliance status and compliant alternatives to avoid costly substitutions.

Instructions

[PRO] Checks whether a specific material, product, or component meets the code requirements for a given trade application and jurisdiction. Returns COMPLIANT, NON_COMPLIANT, or REQUIRES_VERIFICATION with the specific clause that governs the material selection, and — if non-compliant — the compliant alternative. Use this tool BEFORE ordering materials to avoid costly substitutions on site. Do NOT use this tool for general compliance questions — use check_compliance instead. Example inputs: '2.5mm2 TPS cable for 20A underground direct burial circuit NSW', 'Class 12 copper pipe for domestic hot water NSW', 'R3.5 glasswool batts for external wall cavity UK Building Regs'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tradeYesThe trade context for this material check.
regionYesJurisdiction. Determines which product standards and approval schemes apply.
materialYesThe material or product to check. Include: product name or type, specification or rating, and manufacturer if known. Example: '2.5mm2 TPS twin and earth, 450/750V rating, PVC insulation'.
use_caseNoWhere and how the material will be used. Include installation method, environmental conditions, load. Example: 'underground direct burial, 20A circuit, 30m run, clay soil'.standard installation
roleNoRole of the person checking the material.Journeyman
api_keyNoPro API key required.
Behavior4/5

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

No annotations provided, so description covers return values (COMPLIANT, NON_COMPLIANT, REQUIRES_VERIFICATION) and behavior (returns clause and alternative). It does not disclose detailed error handling or rate limits, but is fairly comprehensive for a read-only check.

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?

Description is somewhat lengthy but well-structured: purpose first, then usage guidance, examples, and parameter hints. Could be slightly tighter but remains effective.

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?

No output schema, but description explains return values. Covers all parameters implicitly. Lacks details on API key authentication but sufficient for agent invocation.

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 description coverage is 100%, providing baseline 3. Description adds value with example inputs and context for 'material' and 'use_case' parameters, enhancing understanding beyond 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 checks material compliance against code for a specific trade and jurisdiction, returning compliance status, clause, and alternative. It distinguishes from sibling tool 'check_compliance'.

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?

Explicitly advises using before ordering materials and warns against using for general compliance questions, directing to 'check_compliance' instead.

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