Skip to main content
Glama

ScanBIM MCP

by io.scanbimlabs

acc_create_rfi

Create a Request For Information in ACC Build's RFIs module via the APS Construction RFIs v1 API, in 'draft' status. Returns the ACC rfi_id. When to use: a trade or subcontractor needs formal information from the design team (unclear detail, conflicting spec, missing dimension) and you want a tracked paper trail. When NOT to use: the item is just a punchlist fix — use acc_create_issue. The question is internal to one trade — handle inside that trade's toolchain. APS scopes: data:read data:write account:read 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; 403 scope or resource permission denied (app not provisioned for the project's ACC account, or RFIs module not enabled); 404 project_id not found — check the ID; 429 rate limited — backoff and retry; 5xx APS upstream outage — retry with jitter. Side effects: NON-IDEMPOTENT. Creates a new draft RFI each call. Inserts a row into D1 usage_log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesShort RFI subject line, 1-255 chars. Appears as the RFI headline in ACC.
priorityNoRFI priority. Defaults to 'medium'.
questionYesFull question body sent to the design team. Plain text with newlines allowed.
project_idYesACC project ID in 'b.<uuid>' or '<uuid>' form (the 'b.' prefix is stripped automatically). Obtainable via acc_list_projects.
assigned_toNoACC user ID (UUID) or email of the responder. Pass null or omit to leave unassigned.
linked_clash_idNoOptional clash ID from detect_clashes output used to link this RFI back to the triggering clash. Stored for ScanBIM cross-referencing; not forwarded to ACC.
linked_model_idNoOptional APS URN of the model the RFI references. Stored for ScanBIM cross-referencing; not forwarded to ACC.

Schema Changelog

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

  1. Changed14 schema fields changed
    • addedInput schema / properties / assigned_to / description
      Added value: +"ACC user ID (UUID) or email of the responder. Pass null or omit to leave unassigned."
    • addedInput schema / properties / assigned_to / examples
      Added value: +[
+  "architect@designfirm.com"
+]
    • addedInput schema / properties / linked_clash_id / description
      Added value: +"Optional clash ID from detect_clashes output used to link this RFI back to the triggering clash. Stored for ScanBIM cross-referencing; not forwarded to ACC."
    • addedInput schema / properties / linked_clash_id / examples
      Added value: +[
+  "Ducts_001_Structural Framing_002"
+]
    • addedInput schema / properties / linked_model_id / description
      Added value: +"Optional APS URN of the model the RFI references. Stored for ScanBIM cross-referencing; not forwarded to ACC."
    • addedInput schema / properties / linked_model_id / examples
      Added value: +[
+  "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1tb2RlbHMvMTcwMDAwMDAwMDAwMF9idWlsZGluZy5ydnQ"
+]
    • addedInput schema / properties / priority / description
      Added value: +"RFI priority. Defaults to 'medium'."
    • addedInput schema / properties / priority / examples
      Added value: +[
+  "high"
+]
    • addedInput schema / properties / project_id / description
      Added value: +"ACC project ID in 'b.<uuid>' or '<uuid>' form (the 'b.' prefix is stripped automatically). Obtainable via acc_list_projects."
    • addedInput schema / properties / project_id / examples
      Added value: +[
+  "b.a4be0c34a-4a01-4b0e-9f1a-123456789abc"
+]
    • addedInput schema / properties / question / description
      Added value: +"Full question body sent to the design team. Plain text with newlines allowed."
    • addedInput schema / properties / question / examples
      Added value: +[
+  "Drawing S2.03 shows 1-hour rating on W18x35 beams but spec 07 81 00 calls for 2-hour. Which governs at Level 3?"
+]
    • addedInput schema / properties / subject / description
      Added value: +"Short RFI subject line, 1-255 chars. Appears as the RFI headline in ACC."
    • addedInput schema / properties / subject / examples
      Added value: +[
+  "Confirm fireproofing thickness on W18 beams at Level 3"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It details side effects (non-idempotent, creates a draft each call, inserts usage log), error codes and handling, rate limits, and required scopes. This goes well beyond what annotations would typically provide.

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 well-structured with clear sections (purpose, usage, scopes, rate limits, errors, side effects). Every sentence adds value, and the most important facts are front-loaded. Despite its length, it remains tight and scannable.

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?

For a mutation tool with no annotations and no output schema, the description covers all critical context: prerequisite scopes, common error responses and remedies, rate limits, non-idempotency, and side effects. It even mentions the return value (rfi_id) and the D1 usage log, making it complete for an agent to invoke correctly.

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 does not add parameter-specific semantics beyond what the schema already provides (e.g., project_id format, assigned_to nullability). The schema itself is thorough with examples and edge-case notes, so no deduction is needed, but no extra credit is earned.

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 clearly states the tool's function: creating an RFI in draft status via the APS RFIs API, and explicitly distinguishes it from the sibling tool acc_create_issue by specifying when to use it. The verb 'Create' plus the resource 'Request For Information' and module 'ACC Build's RFIs' make the purpose unambiguous.

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 provides explicit 'When to use' and 'When NOT to use' sections with concrete scenarios and names the alternative tool (acc_create_issue) for punchlist fixes. This gives an AI agent clear decision criteria for selecting this tool over siblings.

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