Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Check NEC working clearance for a panel

find_clearance
Read-onlyIdempotent

Check whether the NEC 110.26 working clearance zone in front of an electrical panel is clear or intruded in 3D. Target the panel by external_id or name substring to get the zones and intruders.

Instructions

Check an electrical panel's NEC 110.26 working clearance in 3D.

Use this to answer "is the working space in front of this panel clear?" The backend builds the code-required clearance zone(s) in true 3D and reports whether anything intrudes. Pass the returned draw block to the draw_clearance viewer command to show the zones (green clear, red intruded); this tool does NOT change the view by itself.

Target the panel either by external_id or by a description substring that must resolve to exactly one panel. If the description matches none or several, the result says so — ask the user to clarify.

The check is directional (projected off the panel's working face) when the panel is mounted on a wall or column, and an honest all-around maintenance-access check when the panel is freestanding — the mode and rule fields say which, and the all-around mode is labeled as NEC-derived guidance rather than the literal front-only rule.

Example: - By id: external_id= - By name: description="circuit breaker switchboard"

Returns: {"external_id", "asset_type", "description", "mode", "rule", "mounting_surface", "clearance": {"zones": [...]}, "intruders": [{external_id, asset_type, description}], "clear": bool|None, "draw": {...}}. clear is None when no rule is defined for the category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_clearance"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoThe element category. v1 supports electrical_panels only; the clearance rule is NEC 110.26 working space.electrical_panels
descriptionNoA substring of the panel's name (e.g. 'circuit breaker switchboard'). The backend resolves it to the single matching electrical panel. Provide this OR external_id; prefer it when the user names the panel so you need not look up an id first.
external_idNoThe externalId of the electrical panel to check. Provide this OR description. Get an id from find_by_category(category='electrical_panels') when you have one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial traits beyond them: no view mutation, directional vs. all-around mode depending on mounting surface, the fact that all-around mode is labeled NEC-derived guidance, and that `clear` is None when no rule exists. These are exactly the non-obvious behaviors an agent needs before interpreting the result.

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, then usage, then targeting, then an example, then returns — a logical progression with no filler sentences. The returns block partly restates fields already present in the output schema; it is justified mainly for the `clear=None` semantics, so a small deduction for 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?

For a three-parameter read tool with a full output schema and rich annotations, the description covers selection, targeting, ambiguity handling, result interpretation (mode/rule/clear), and the visualization handoff. Nothing an agent needs in order to call it or read its result is missing.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the resolution contract — the description substring must resolve to exactly one panel, and zero or multiple matches produce a reported failure. That adds error-case meaning the schema only hints at, though precedence between description and external_id is stated more fully in the schema than here.

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 opening sentence names a specific verb and resource — 'Check an electrical panel's NEC 110.26 working clearance in 3D' — plus the user question it answers. No sibling tool performs a clearance analysis, so the agent can select it unambiguously from find_by_category, highlight_elements, or isolate.

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?

It states the triggering question ('is the working space in front of this panel clear?'), both targeting strategies, and the ambiguity fallback ('ask the user to clarify'). It also names the follow-up tool (draw_clearance) for visualization and explicitly says this tool does NOT change the view, which prevents a wrong next-action inference.

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