Revit Model MCP

Overview Schema Source Related Servers Discussions Admin

Check NWC Settings

revit_nwc_settings_check

Read-onlyIdempotent

Validate Navisworks NWC exporter XML settings on a Revit workstation without running an export, and report skipped entries that make results incomplete.

Instructions

Parse a Navisworks exporter XML file on the Revit workstation without exporting. A non-empty skipped list means the result is incomplete; skippedCount counts all skipped entries.

Input Schema

Name	Required	Description
`document`	No	Title or file name substring of the target document; needed when several Revit instances run.
`process_id`	No	Revit process ID; takes precedence over document.
`settings_xml`	Yes
`timeout_seconds`	No	Seconds to wait for a result (default 120).
`pickup_timeout_seconds`	No	Seconds to wait for the add-in to pick up the job (default 300); unused over HTTP.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.10.0Oct 14, 2026

changedInput schema / properties / document / description

Previous value: -"Case-insensitive substring of the target active document title or file name. Reads require exactly one matching instance; omitted document requires exactly one running instance. Zero or multiple matches fail before publishing. revit_list_instances returns all matching instances, or all running instances when omitted."New value: +"Title or file name substring of the target document; needed when several Revit instances run."

removedInput schema / properties / document / title
```
Removed value: -"Document"
```

changedInput schema / properties / pickup_timeout_seconds / description

Previous value: -"Positive integer seconds to wait for the add-in to pick up a local or SSH job (300 when omitted); ignored over HTTP. A pickup timeout raises an error but the pending job may still execute later."New value: +"Seconds to wait for the add-in to pick up the job (default 300); unused over HTTP."

removedInput schema / properties / pickup_timeout_seconds / title
```
Removed value: -"Pickup Timeout Seconds"
```

changedInput schema / properties / process_id / description

Previous value: -"Exact positive Revit process ID. Takes precedence over document; if both are supplied they must agree."New value: +"Revit process ID; takes precedence over document."

removedInput schema / properties / process_id / title
```
Removed value: -"Process Id"
```
removedInput schema / properties / settings_xml / title
```
Removed value: -"Settings Xml"
```

changedInput schema / properties / timeout_seconds / description

Previous value: -"Positive integer seconds to wait for a result after pickup (120 when omitted); HTTP uses this as its response budget. Expiry raises an error, and increasing it does not override the add-in's execution limits."New value: +"Seconds to wait for a result (default 120)."

removedInput schema / properties / timeout_seconds / title
```
Removed value: -"Timeout Seconds"
```

removedInput schema / title

Removed value: -"revit_nwc_settings_checkArguments"

removedOutput schema / title

Removed value: -"revit_nwc_settings_checkDictOutput"

Addedv0.7.0Sep 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile. The description adds genuine extra context: parsing occurs on the Revit workstation without triggering an export, and it warns that a non-empty skipped list makes the result incomplete with skippedCount counting skipped entries.

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 tightly scoped sentences with zero filler, and the core purpose is front-loaded. The second sentence concerns output semantics, which is slightly tangential but still earns its place as a correctness warning.

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

Completeness4/5

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

With an output schema present and 80% parameter coverage, the definition needn't restate return values, yet it still adds the critical caveat about incomplete results via the skipped list. For a read-only inspection tool this is essentially complete, missing only explicit sibling routing.

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 80%, so the schema already documents document, process_id, and the timeout parameters. The description contributes no additional parameter meaning, only output semantics, so the baseline 3 applies.

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 (parse) and resource (Navisworks exporter XML on the Revit workstation), and the phrase 'without exporting' implicitly contrasts it with export-oriented siblings. It does not name revit_export_nwc explicitly, so sibling differentiation is implied rather than stated.

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?

'Without exporting' hints at the use context (inspecting settings rather than performing an export), which implies when an agent would prefer this over revit_export_nwc. However, there is no explicit when-to-use, when-not, or prerequisite guidance, leaving routing to inference.

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

Deploy Server