Skip to main content
Glama

ScanBIM MCP

by io.scanbimlabs

twinmotion_render

Queue a photorealistic Twinmotion-style still render of a translated model with time-of-day, weather, season, and resolution controls. Returns a render_id and preview_url; the actual render pipeline is a ScanBIM roadmap item (Week 5 buildout), so today this tool responds synchronously with a stub job descriptor. When to use: you want a scripted way to request a hero still for a proposal or client deck. When NOT to use: you need real-time interactive rendering — use get_viewer_link. You need a moving camera — use twinmotion_walkthrough. You expect the image file bytes back in the response — this tool returns a URL, not bytes. APS scopes: none today (render pipeline is ScanBIM-internal); viewables:read data:read will apply when the pipeline goes live. 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 (will apply when pipeline is live); 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 render_id (tm_). Inserts a row into D1 usage_log. When the pipeline is live it will create a rendering job on ScanBIM's compute backend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoVegetation and ground-cover preset. Defaults to 'summer'.
weatherNoSky and atmospheric preset. Defaults to 'clear'.
model_idYesAPS URN (base64url-encoded, starts with 'dXJu', unpadded) of the model to render.
resolutionNoOutput image resolution. Defaults to '4k'.
time_of_dayNoSun angle preset driving lighting, shadows, and sky. Defaults to 'noon'.
camera_presetNoNamed camera viewpoint (e.g. 'hero-exterior', 'lobby-entry'). Free-form string passed through to the render pipeline.

Schema Changelog

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

  1. Changed12 schema fields changed
    • addedInput schema / properties / camera_preset / description
      Added value: +"Named camera viewpoint (e.g. 'hero-exterior', 'lobby-entry'). Free-form string passed through to the render pipeline."
    • addedInput schema / properties / camera_preset / examples
      Added value: +[
+  "hero-exterior"
+]
    • addedInput schema / properties / model_id / description
      Added value: +"APS URN (base64url-encoded, starts with 'dXJu', unpadded) of the model to render."
    • addedInput schema / properties / model_id / examples
      Added value: +[
+  "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1tb2RlbHMvMTcwMDAwMDAwMDAwMF9idWlsZGluZy5ydnQ"
+]
    • addedInput schema / properties / resolution / description
      Added value: +"Output image resolution. Defaults to '4k'."
    • addedInput schema / properties / resolution / examples
      Added value: +[
+  "4k"
+]
    • addedInput schema / properties / season / description
      Added value: +"Vegetation and ground-cover preset. Defaults to 'summer'."
    • addedInput schema / properties / season / examples
      Added value: +[
+  "autumn"
+]
    • addedInput schema / properties / time_of_day / description
      Added value: +"Sun angle preset driving lighting, shadows, and sky. Defaults to 'noon'."
    • addedInput schema / properties / time_of_day / examples
      Added value: +[
+  "dusk"
+]
    • addedInput schema / properties / weather / description
      Added value: +"Sky and atmospheric preset. Defaults to 'clear'."
    • addedInput schema / properties / weather / examples
      Added value: +[
+  "partly_cloudy"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels. It discloses that the endpoint currently responds with a 'stub job descriptor' rather than performing an actual render, details side effects ('NON-IDEMPOTENT', mints new render_id, inserts D1 usage_log), error codes (401/403/404/429/5xx), rate limits, and required APS scopes. This is far beyond typical transparency.

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?

The description is well-structured with clear sections (purpose, when/when-not, scopes, rate limits, errors, side effects) and front-loaded with a concise one-sentence purpose. While lengthy, each section carries unique operational information needed to use the tool correctly; the length is justified by the tool's current stub status and future behavior.

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?

The description is fully self-contained for a tool with no output schema and no annotations. It defines return values (render_id, preview_url), current stub behavior, side effects, error handling, rate limits, scopes, and explicit alternative tools. It also notes future pipeline behavior and emphasizes the 'translated model' prerequisite, making it complete for an agent to decide and invoke.

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%, so the baseline is 3. The description adds no additional parameter meaning beyond listing control categories ('time-of-day, weather, season, and resolution') that already appear in the schema. It does not enhance the schema's examples or field descriptions.

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 specifies a concrete action: 'Queue a photorealistic Twinmotion-style still render of a translated model' with render controls. It clearly differentiates from siblings by stating this is for 'still renders' and explicitly provides alternatives (get_viewer_link for real-time, twinmotion_walkthrough for moving cameras).

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?

The description includes dedicated 'When to use' and 'When NOT to use' sections, presenting explicit use cases (hero still for proposals/client decks) and exclusions with alternatives (real-time interactive rendering -> get_viewer_link; moving camera -> twinmotion_walkthrough; expecting bytes -> returns URL). It also warns that the pipeline is a stub today, setting expectations.

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