Model MCP

Overview Schema Source Related Servers Discussions Admin

Start batch collection

revit_batch_start

Start a persistent, read-only batch run across local, UNC, or RSN Revit models, with a configurable per-model open deadline for large or slow-opening files.

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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revit_batch_start"
  }
}

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

C2.9/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description adds useful context: the run is 'persistent' (state is created, explaining the non-read-only annotation) and 'read-only' over the models themselves, plus the accepted model sources (local, UNC, RSN). However, it never says the run is asynchronous or that progress/results must be retrieved via revit_batch_status and revit_batch_fetch, which is the critical behavioral fact for a 'start' tool. There is mild tension between 'read-only run' and readOnlyHint=false, though it is reconcilable as read-only over the models while creating persistent job state.

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?

Two sentences, no filler, and the core capability is front-loaded before the parameter note. The brevity is efficient but borders on under-specification given six undocumented parameters.

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 six-parameter, zero-coverage, job-initiating tool with an output schema, the description is far too thin: it omits how models are selected (paths vs folder vs years), what recursive and parameter_rules do, and that the returned run must be polled. The output schema means return values need not be described, but the invocation semantics and async workflow are missing.

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% across six parameters, and the description explains only open_timeout_minutes, giving its default and the conditional 45-minute default when upgrading in memory — a genuinely useful detail. The other five parameters (paths, years, folder, recursive, parameter_rules) are left entirely undefined in both schema and description, including the key question of whether paths, folder, or years is the required input selector. The description therefore compensates for only one sixth of the coverage gap.

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?

The description states a specific verb and resource — 'Start a persistent, read-only run over local, UNC or RSN models' — so an agent knows this initiates a batch collection job rather than reporting on one. The word 'Start' implicitly separates it from the revit_batch_status / revit_batch_cancel / revit_batch_fetch siblings, but those siblings are never named, so the differentiation is left to inference.

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?

There is no statement of when to use this tool versus alternatives such as revit_process_models, nor any mention of the companion lifecycle tools (revit_batch_status, revit_batch_fetch, revit_batch_cancel) that an agent must call after starting a run. The word 'Start' hints at a lifecycle but no condition, prerequisite, or exclusion is given.

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

Deploy Server