Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Find the assets inside a room

find_in_room
Read-onlyIdempotent

Find tracked assets whose 3D bounding-box centers fall inside a room's floor-to-ceiling volume, filter by category, and return external IDs to highlight or isolate.

Instructions

Find the tracked assets that sit inside a room's 3D volume.

Use this to answer room-contents questions (e.g. "what equipment is in room 54?", "the receptacles in the electrical room"), then pass the returned external_ids to highlight_elements or isolate. This tool does NOT change the view by itself.

Membership is by true 3D containment: an asset's bounding-box center must fall inside the room footprint AND within its floor-to-ceiling band, so assets on other floors are correctly excluded.

Examples: - Everything in room 54: room_number='54' - Just the receptacles: room_number='54', category='receptacles'

Returns: {"room": {external_id, room_name, room_number, level_name}, "count": int, "elements": [{external_id, asset_type, description, level_name}]}.

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_in_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax assets to return (1-500).
categoryNoOptional category to restrict the result to (e.g. only the receptacles in the room). Omit for all tracked assets.
room_numberNoThe room's number as shown on the plans (e.g. '54' for 'EDP I'). Provide this or room_external_id.
room_external_idNoThe room's durable externalId. An alternative to room_number.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds real behavior: no view mutation, and the exact 3D containment rule (bounding-box center inside footprint AND floor-to-ceiling band) that explains why other-floor assets are excluded - a non-obvious correctness detail an agent would otherwise mispredict.

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/alternatives, then semantics, then examples - a sensible ordering with no filler prose. The 'Returns:' block is largely redundant with the declared output schema and is the one section that does not fully earn its space.

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 a rich schema, full annotations, and an output schema, the description supplies exactly the missing pieces: containment semantics, the view-immutability guarantee, and the downstream highlight/isolate workflow. Nothing an agent needs to call this correctly is absent.

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 baseline is 3, but the worked examples show the practical combination pattern (room_number alone vs. room_number plus category) that the schema only documents field-by-field. The category constraint's effect on narrowing results within a room is made concrete rather than left to inference.

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?

States a specific verb and resource plus its scope: 'Find the tracked assets that sit inside a room's 3D volume.' The containment criterion and the room-scoped framing let an agent separate it from catalog-wide siblings like find_by_category and find_elements without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete trigger questions ('what equipment is in room 54?') and an explicit handoff pattern - pass returned external_ids to highlight_elements or isolate - plus the caveat that this tool does not change the view. It stops short of stating when to prefer a sibling (e.g. a category sweep across all rooms), so no explicit negative routing.

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