Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Zoom to

zoom_to
Read-onlyIdempotent

Frames a room or selected elements by moving the BIM camera; use it when a user asks to zoom in on a highlighted room or a set of elements.

Instructions

Move the camera to frame a room or a set of elements.

This is the only tool that changes the view — use it only when the user asks to zoom in on something. Provide a room via space_external_id, or a set of elements via external_ids. A room takes precedence if both are given. To frame a room it must already be highlighted (highlight_rooms).

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": "zoom_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
external_idsNoRevit UniqueIds of elements to frame. Ignored if space_external_id is given.
space_external_idNoRevit UniqueId of a single room/space to frame. Takes precedence over external_ids. The room must already be highlighted.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and openWorldHint, so the safety profile is covered; the description adds the meaningful nuance that this is the sole view-changing tool and discloses a non-obvious pre-condition (the room must already be highlighted). What it omits is what happens on failure or whether the camera change persists across other calls.

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 the purpose and the exclusivity claim, then the when-to-use constraint, then the parameter routing. Slightly repetitive since the precedence rule appears both here and in the schema, but no sentence is wasted.

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?

For a 2-parameter, zero-required tool with a full output schema and complete annotations, this covers purpose, trigger condition, input routing, and the highlight prerequisite. Minor gaps remain around behavior when an id is unknown or does not resolve to a framed element.

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 both parameters already document precedence ("Ignored if space_external_id is given", "Takes precedence over external_ids"). The description restates the same precedence and highlight requirement rather than adding new semantics, so 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?

Names a specific verb and object ("Move the camera to frame a room or a set of elements") and explicitly claims the scope: "This is the only tool that changes the view." An agent can immediately distinguish it from siblings like highlight_rooms, isolate, and reset without reading any 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?

Gives a clear when-to-use rule ("use it only when the user asks to zoom in on something"), states the two mutually exclusive input modes, and resolves their conflict ("A room takes precedence if both are given"). It also names the prerequisite sibling tool (highlight_rooms) needed before framing a room.

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