Skip to main content
Glama

ScanBIM MCP

by io.scanbimlabs

xr_launch_vr_session

Create a shareable WebXR VR walkthrough session URL (and Meta Quest oculus:// deep link + QR code) for a translated model. The session_id is generated server-side; rendering happens in the user's Quest browser. When to use: you need to walk a client or field team through a model in immersive VR on Meta Quest 2/3/Pro. When NOT to use: the user is on a phone/tablet without a headset — use xr_launch_ar_session or get_viewer_link. The model has not finished translating — call get_model_metadata first. APS scopes: viewables:read data:read (enforced at viewer page load, not at tool call). Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable. Errors: 401 APS token expired/invalid — refresh (only at viewer page load); 403 scope or resource permission denied; 404 URN not found — check the ID; 429 rate limited — backoff and retry; 5xx APS upstream outage — retry with jitter. Side effects: NON-IDEMPOTENT. Each call mints a new session_id (vr_). Inserts a row into D1 usage_log which is later read by xr_list_sessions. No APS resources are created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idYesAPS URN (base64url-encoded, starts with 'dXJu', unpadded) of the model to load in VR.
session_nameNoHuman-readable session label shown in the session list. Defaults to 'VR Session' if omitted.
max_participantsNoMaximum concurrent participants in multi-user mode. Integer 1-20. Defaults to 5.
enable_measurementsNoEnable in-VR tape-measure tool. Defaults to true.
enable_voice_annotationsNoEnable voice-note recording anchored to model elements. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changed
    • addedInput schema / properties / enable_measurements / description
      Added value: +"Enable in-VR tape-measure tool. Defaults to true."
    • addedInput schema / properties / enable_measurements / examples
      Added value: +[
+  true
+]
    • addedInput schema / properties / enable_voice_annotations / description
      Added value: +"Enable voice-note recording anchored to model elements. Defaults to false."
    • addedInput schema / properties / enable_voice_annotations / examples
      Added value: +[
+  false
+]
    • addedInput schema / properties / max_participants / description
      Added value: +"Maximum concurrent participants in multi-user mode. Integer 1-20. Defaults to 5."
    • addedInput schema / properties / max_participants / examples
      Added value: +[
+  5
+]
    • addedInput schema / properties / model_id / description
      Added value: +"APS URN (base64url-encoded, starts with 'dXJu', unpadded) of the model to load in VR."
    • addedInput schema / properties / model_id / examples
      Added value: +[
+  "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1tb2RlbHMvMTcwMDAwMDAwMDAwMF9idWlsZGluZy5ydnQ"
+]
    • addedInput schema / properties / session_name / description
      Added value: +"Human-readable session label shown in the session list. Defaults to 'VR Session' if omitted."
    • addedInput schema / properties / session_name / examples
      Added value: +[
+  "Owner walkthrough - Level 3 MEP"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are present, so the description fully carries the transparency burden. It discloses side effects (non-idempotent, session_id minting, D1 usage_log insert, no APS resources created), APS scopes, rate limits, and detailed error codes with remedies. This goes well beyond typical descriptions.

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?

The description is long but logically structured into clear sections (purpose, when to use, when not to use, scopes, rate limits, errors, side effects). Every sentence delivers actionable information; there is no redundancy or 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?

Given the tool's complexity, no annotations, and no output schema, the description covers all critical aspects: purpose, usage constraints, scopes, rate limits, error handling, and side effects. It even notes that rendering happens in the user's Quest browser, setting correct expectations.

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 description coverage is 100% with examples and defaults for all five parameters. The description adds a useful note that session_id is generated server-side, but it does not add per-parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 description opens with a specific verb and resource: 'Create a shareable WebXR VR walkthrough session URL (and Meta Quest oculus:// deep link + QR code) for a translated model.' It clearly distinguishes from siblings by explicitly naming xr_launch_ar_session and get_viewer_link as alternatives for non-headset users.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, including the exact alternative tools (xr_launch_ar_session, get_viewer_link) and a prerequisite check (get_model_metadata before calling if translation may be incomplete). This is exemplary usage guidance.

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

All ScanBIM MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Tools are grouped by domain with clear prefixes (acc_, xr_, get_) and each has a distinct purpose. The only potential confusion is between lumion_render and twinmotion_render, but descriptions clarify the aesthetic difference. Overall, tools are clearly differentiated.

Naming Consistency4/5

Most tools follow consistent patterns: acc_* for ACC operations, get_* for metadata retrieval, and xr_launch_*/xr_list_* for XR sessions. Minor deviations like list_models instead of get_models and render tools using software names as prefixes are readable and do not hinder pattern recognition.

Tool Count4/5

At 19 tools, the count is slightly above the ideal range but justified by the server's broad scope covering ACC, model translation, clash detection, rendering, and XR. Some render tools are stubs and could be trimmed, but they are clearly marked as roadmap items.

Completeness3/5

The set covers upload→translate→view→clash-detect→create issues/RFIs workflows well, but lacks update/delete operations for issues and RFIs, and there is no full-detail retrieval for a single issue or RFI. These gaps can cause workflow dead ends for closeout and status changes.

Resources