Skip to main content
Glama

ScanBIM MCP

by io.scanbimlabs
OverviewDiscussionsAdmin

acc_list_rfis

List up to 50 RFIs from an ACC project, optionally filtered by status. Returns a normalized array of {id, subject, status}. When to use: you need a quick rollup of outstanding or answered RFIs on a project, or to find a specific RFI id. When NOT to use: you want the full response thread of a single RFI — use the ACC UI or per-RFI endpoint. This tool caps at 50 results and does no pagination. APS scopes: data:read 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 (RFIs module may not be enabled on the project); 404 project_id not found — check the ID; 429 rate limited — backoff and retry; 5xx APS upstream outage — retry with jitter. Side effects: READ-ONLY. Inserts a row into D1 usage_log. Idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by RFI status. Common values: 'draft', 'open', 'answered', 'closed', 'void'. Omit for all.
project_idYesACC project ID in 'b.<uuid>' or '<uuid>' form (the 'b.' prefix is stripped automatically).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / project_id / description
      Added value: +"ACC project ID in 'b.<uuid>' or '<uuid>' form (the 'b.' prefix is stripped automatically)."
    • addedInput schema / properties / project_id / examples
      Added value: +[
+  "b.a4be0c34a-4a01-4b0e-9f1a-123456789abc"
+]
    • addedInput schema / properties / status / description
      Added value: +"Filter by RFI status. Common values: 'draft', 'open', 'answered', 'closed', 'void'. Omit for all."
    • addedInput schema / properties / status / examples
      Added value: +[
+  "open"
+]
  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, the description fully discloses behaviors: 'Side effects: READ-ONLY. Inserts a row into D1 usage_log. Idempotent.' It also lists APS scopes, rate limits, and detailed error handling. It states the return shape and limits, leaving little hidden behavior.

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 structured with a clear opening purpose, then usage, then technical details in labeled sections. While longer than some, every sentence serves a purpose—scopes, errors, side effects—and it is front-loaded with the primary action.

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?

Although there is no output schema, the description gives the return array shape: '{id, subject, status}'. It also covers error handling, rate limits, side effects, and limits (50 max, no pagination), making it fully contextual for a list operation.

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 the schema already describes both parameters with examples and prefix-stripping behavior. The description itself adds no parameter-specific detail beyond the initial mention of status filtering, so the baseline of 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: 'List up to 50 RFIs from an ACC project, optionally filtered by status.' This clearly distinguishes it from sibling tools like acc_create_rfi and acc_list_issues, and clarifies scope by stating it does not include full response threads.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance, including an alternative: 'use the ACC UI or per-RFI endpoint.' It also notes the 50-result cap and lack of pagination, helping an agent decide if this tool fits the task.

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.

Resources