Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Highlight rooms

highlight_rooms
Read-onlyIdempotent

Draw translucent volumes around specified rooms or spaces in the BIM viewer to visually highlight them without moving the camera; invalid or duplicate IDs are ignored.

Instructions

Draw translucent volumes for a set of rooms/spaces in the viewer.

The room volumes are added in place; the camera does NOT move. Invalid or duplicate ids are dropped.

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": {
      "space_external_ids": "<space_external_ids>"
    },
    "name": "highlight_rooms"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_external_idsYesRevit UniqueIds (the viewer's externalIds) of rooms/spaces to highlight. 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

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description isn't carrying the safety burden. It still adds real context beyond them: volumes are added in place, the camera is left untouched, and invalid or duplicate ids are silently dropped — a meaningful mutation-free side effect worth knowing.

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?

Two short sentences with the core action front-loaded and the camera/edge-case caveats immediately after. Every clause conveys information an agent would otherwise have to guess at.

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?

With a single fully documented parameter, rich annotations, and an output schema, the description covers everything needed to invoke the tool correctly. The one minor omission is how highlights are removed — likely handled by the reset sibling — which the description never mentions.

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 GUID format and shape are already documented, setting the baseline at 3. The description adds handling semantics for those ids — that invalid and duplicate entries are dropped rather than erroring — which is meaning the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource: it draws translucent volumes for rooms/spaces in the viewer, which is narrower than the generic highlight_elements sibling. It is clear what the tool produces, though it never names the sibling it differs from, so the agent must infer the room-vs-element distinction.

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

Usage Guidelines3/5

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

The line 'the camera does NOT move' implicitly steers an agent away from camera-moving siblings like zoom_to, which is useful contextual guidance. However, there is no explicit when-to-use/when-not-to-use statement or named alternative, so selection is only implied.

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