Revit Model MCP

Overview Schema Source Related Servers Discussions Admin

Load Families

revit_load_family

Destructive

Load one or more workstation .rfa family files into an open Revit model as one undo entry, skipping existing families unless overwrite is enabled.

Instructions

Load workstation .rfa files in one undo entry. Existing families are skipped unless overwrite is true.

Input Schema

Name	Required	Description
`paths`	Yes
`dry_run`	No
`document`	No	Title or file name substring of the target open document; needed when several are open.
`overwrite`	No
`timeout_seconds`	No
`overwrite_parameter_values`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.10.0Oct 14, 2026

changedInput schema / properties / document / description

Previous value: -"Case-insensitive substring of the target open document's title or file name. Required to disambiguate when the Revit process has more than one document open; omit only when a single document is open (the active document is used). An unknown or ambiguous reference is rejected before any change."New value: +"Title or file name substring of the target open document; needed when several are open."

removedInput schema / properties / document / title
```
Removed value: -"Document"
```
removedInput schema / properties / dry_run / title
```
Removed value: -"Dry Run"
```
removedInput schema / properties / overwrite / title
```
Removed value: -"Overwrite"
```
removedInput schema / properties / overwrite_parameter_values / title
```
Removed value: -"Overwrite Parameter Values"
```
removedInput schema / properties / paths / title
```
Removed value: -"Paths"
```

removedInput schema / properties / response_timeout_s

Removed value: -{
-  "default": 600,
-  "maximum": 3600,
-  "minimum": 30,
-  "title": "Response Timeout S",
-  "type": "integer"
-}

addedInput schema / properties / timeout_seconds

Added value: +{
+  "default": 600,
+  "maximum": 3600,
+  "minimum": 30,
+  "type": "integer"
+}

removedInput schema / title

Removed value: -"revit_load_familyArguments"

removedOutput schema / title

Removed value: -"revit_load_familyDictOutput"

Addedv0.9.1Oct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety bar is lowered. The description still adds meaningful behavior beyond them: the whole load collapses into 'one undo entry' (atomicity/reversibility) and the skip-vs-overwrite rule explains the non-idempotent semantics. It omits the dry_run preview path and timeout_seconds behavior, so it isn't complete.

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 tight sentences with zero filler; the primary action is front-loaded and the conditional rule follows immediately. Nothing is redundant with the schema or annotations.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations carry the destructive profile. But for a destructive, 6-parameter batch-mutation with 17% schema coverage, the description is thin: it says nothing about dry_run as the safe preview path, document disambiguation when multiple files are open, or timeout behavior.

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 only 17% (just the `document` param), so the description must compensate. It adds real semantics for `overwrite` (skip-existing behavior) and clarifies the nature of `paths` (workstation .rfa files), but leaves dry_run, timeout_seconds, and overwrite_parameter_values unexplained.

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?

Specific verb+resource: loads .rfa family files into Revit, with the scope qualifier 'workstation .rfa files'. That distinguishes it implicitly from siblings like revit_place_family/revit_place_families (instance placement) and revit_edit_families (modification), but no sibling is named explicitly.

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

Usage Guidelines3/5

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

'Existing families are skipped unless overwrite is true' is a real conditional rule that guides invocation. However, no alternatives are named and no when-not-to-use case (e.g. use place_family after loading, or family_audit to inspect) is given, so guidance is implied rather than explicit.

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

Deploy Server