Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Isolate elements

isolate
Read-onlyIdempotent

Show only specified BIM elements and hide the rest without moving the camera; call reset to restore the full model.

Instructions

Isolate a set of elements: show only them and hide the rest.

A stronger focus than highlight_elements — everything outside the set is hidden. The camera does NOT move. Call reset to restore the full model.

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": {
      "external_ids": "<external_ids>"
    },
    "name": "isolate"
  }
}

Input Schema

NameRequiredDescriptionDefault
external_idsYesRevit UniqueIds (the viewer's externalIds) of elements to isolate. Shape: 8-4-4-4-12 hex GUID, hyphen, 8 hex digits.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnly/idempotent/non-destructive and openWorld, but the description adds genuinely useful behavior: the camera does NOT move, everything outside the set is hidden, and reset restores the model. That reversibility and view-only scope are exactly the context an agent needs before mutating viewer state, though it doesn't say what the response returns or how isolated state interacts with subsequent searches.

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?

Three short sentences, front-loaded with the effect, then the comparison, then the undo path. No sentence is filler.

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 an output schema present, rich annotations, and a single fully documented parameter, the description only needed to cover effect, contrast, and reversibility — and it covers all three.

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 coverage is 100% and the external_ids property already documents the Revit UniqueId GUID shape in detail, so the description adds no parameter meaning beyond it. Baseline 3 is appropriate when the schema carries the full burden.

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 first sentence gives a concrete verb ('isolate') plus the exact visible effect ('show only them and hide the rest'), which is unmistakably distinct from highlight_elements. An agent can distinguish it from every listed sibling without opening a schema.

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 explicitly positions itself against the closest alternative ('a stronger focus than highlight_elements') and names the recovery path ('Call reset to restore the full model'). Both when-to-use and how-to-undo are stated, leaving nothing to inference.

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