Revit Model MCP

Overview Schema Source Related Servers Discussions Admin

Start batch collection

revit_batch_start

Read-only

Start a read-only batch run over local, UNC, or RSN Revit models to analyze multiple files with configurable paths, years, and open timeouts.

Instructions

Start a persistent, read-only run over local, UNC or RSN models. open_timeout_minutes is the per-model open deadline (default 30, 45 when upgrading in memory).

Input Schema

Name	Required	Description	Default
`paths`	No
`years`	No
`folder`	No
`recursive`	No
`parameter_rules`	No
`open_timeout_minutes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.10.0Oct 14, 2026
- removedInput schema / properties / folder / title
```
Removed value: -"Folder"
```
- removedInput schema / properties / open_timeout_minutes / title
```
Removed value: -"Open Timeout Minutes"
```
- removedInput schema / properties / parameter_rules / title
```
Removed value: -"Parameter Rules"
```
- removedInput schema / properties / paths / title
```
Removed value: -"Paths"
```
- removedInput schema / properties / recursive / title
```
Removed value: -"Recursive"
```
- removedInput schema / properties / years / title
```
Removed value: -"Years"
```
- removedInput schema / title
```
Removed value: -"revit_batch_startArguments"
```
- removedOutput schema / title
```
Removed value: -"revit_batch_startDictOutput"
```

Changed1 schema field changedv0.9.1Oct 7, 2026

addedInput schema / properties / open_timeout_minutes

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Open Timeout Minutes"
+}

Addedv0.7.0Sep 30, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds useful operational context: the run is persistent, targets local/UNC/RSN models, and open_timeout_minutes defaults to 30 (45 when upgrading in memory). It does not discuss idempotency or job lifecycle, but adds meaningful behavior beyond the annotations.

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?

Two sentences, front-loaded with the core purpose and then a parameter detail. There is no filler or repetition, and the structure is easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter batch-start tool with no required fields and no schema parameter descriptions, the description is far too sparse. It omits what is being collected, how to specify input scopes, and the meaning of most parameters, though the existence of an output schema means return values need not be explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are 6 parameters, so the description carries the burden of explaining them. It only explains open_timeout_minutes, leaving paths, years, folder, recursive, and parameter_rules completely undocumented in both the schema and the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Start') and resource ('persistent, read-only run over local, UNC or RSN models'), making the tool's purpose clear. It does not explicitly differentiate itself from sibling tools such as revit_batch_status or revit_batch_cancel, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It only implies usage by saying it starts a batch run, leaving the agent to infer when this should be chosen over revit_process_models or the other batch lifecycle tools.

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

Deploy Server