Model MCP

Overview Schema Source Related Servers Discussions Admin

Export Navisworks NWC

revit_export_nwc

Destructive

Export Revit models, views, or selections to an NWC file at a specified workstation path using the Navisworks exporter, with options for overwrite confirmation and export settings.

Instructions

Save an NWC file to a folder the user names through path on the Revit workstation; needs the Navisworks exporter. settings_xml applies exporter XML values, explicit arguments take precedence. Replacing an existing file (overwrite=true) uses a two-step confirm_token handshake with the AI app. The AI app is expected to show the action to you; Model MCP does not show its own dialog. May commit; revit_jobs polls; retry repeats.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "revit_export_nwc"
  }
}

Input Schema

Name	Required	Description
`path`	Yes
`view`	No
`scope`	No
`dry_run`	No
`document`	No	Title or file name substring of the target open document; needed when several are open.
`overwrite`	No
`parameters`	No
`coordinates`	No
`element_ids`	No
`export_urls`	No
`export_links`	No
`export_parts`	No
`settings_xml`	No
`confirm_token`	No
`convert_lights`	No
`faceting_factor`	No
`timeout_seconds`	No
`export_element_ids`	No
`export_room_geometry`	No
`find_missing_materials`	No
`divide_file_into_levels`	No
`export_room_as_attribute`	No
`convert_element_properties`	No
`convert_linked_cad_formats`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedv0.10.0Oct 14, 2026
- removedInput schema / properties / confirm_token / title
```
Removed value: -"Confirm Token"
```
- removedInput schema / properties / convert_element_properties / title
```
Removed value: -"Convert Element Properties"
```
- removedInput schema / properties / convert_lights / title
```
Removed value: -"Convert Lights"
```
- removedInput schema / properties / convert_linked_cad_formats / title
```
Removed value: -"Convert Linked Cad Formats"
```
- removedInput schema / properties / coordinates / title
```
Removed value: -"Coordinates"
```
- removedInput schema / properties / divide_file_into_levels / title
```
Removed value: -"Divide File Into Levels"
```
- 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 / element_ids / title
```
Removed value: -"Element Ids"
```
- removedInput schema / properties / export_element_ids / title
```
Removed value: -"Export Element Ids"
```
- removedInput schema / properties / export_links / title
```
Removed value: -"Export Links"
```
- removedInput schema / properties / export_parts / title
```
Removed value: -"Export Parts"
```
- removedInput schema / properties / export_room_as_attribute / title
```
Removed value: -"Export Room As Attribute"
```
- removedInput schema / properties / export_room_geometry / title
```
Removed value: -"Export Room Geometry"
```
- removedInput schema / properties / export_urls / title
```
Removed value: -"Export Urls"
```
- removedInput schema / properties / faceting_factor / title
```
Removed value: -"Faceting Factor"
```
- removedInput schema / properties / find_missing_materials / title
```
Removed value: -"Find Missing Materials"
```
- removedInput schema / properties / overwrite / title
```
Removed value: -"Overwrite"
```
- removedInput schema / properties / parameters / title
```
Removed value: -"Parameters"
```
- removedInput schema / properties / path / title
```
Removed value: -"Path"
```
- removedInput schema / properties / response_timeout_s
```
Removed value: -{
-  "default": 1800,
-  "maximum": 3600,
-  "minimum": 30,
-  "title": "Response Timeout S",
-  "type": "integer"
-}
```
- removedInput schema / properties / scope / title
```
Removed value: -"Scope"
```
- removedInput schema / properties / settings_xml / title
```
Removed value: -"Settings Xml"
```
- addedInput schema / properties / timeout_seconds
```
Added value: +{
+  "default": 1800,
+  "maximum": 3600,
+  "minimum": 30,
+  "type": "integer"
+}
```
- removedInput schema / properties / view / title
```
Removed value: -"View"
```
- removedInput schema / title
```
Removed value: -"revit_export_nwcArguments"
```
- removedOutput schema / title
```
Removed value: -"revit_export_nwcDictOutput"
```

Changed1 schema field changedv0.9.1Oct 7, 2026

addedInput schema / properties / confirm_token

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Confirm Token"
+}

Addedv0.7.0Sep 30, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: overwrite triggers a two-step confirm_token handshake, the AI app (not Model MCP) is responsible for showing the action to the user, and settings_xml values are overridden by explicit arguments. The phrase 'May commit' is cryptic about what side effects occur on the document, which keeps it from a 5.

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?

The core action is front-loaded in the first sentence and there is no filler. The telegraphic tail ('May commit; revit_jobs polls; retry repeats.') is compact but reads as shorthand that costs some clarity.

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 no explanation, and the overwrite/permission workflow is covered. For a 24-parameter export tool with 4% schema coverage, the description leaves most export options semantically unexplained, which is a meaningful gap even though the invocation path (path, overwrite, confirm_token) is clear.

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 only 4%, so the description must carry the parameter burden, yet it explains only path, overwrite/confirm_token, and settings_xml precedence. The remaining ~20 exporter options (scope, coordinates, faceting_factor, divide_file_into_levels, element_ids, timeout_seconds, etc.) get no meaning beyond their bare names.

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 first clause names a specific verb and artifact: save an NWC file to a user-named folder path on the Revit workstation, and it notes the Navisworks exporter dependency. It is clearly distinguishable from the generic revit_export and revit_export_view because the output format is stated, though it never names those siblings 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?

It gives a prerequisite (Navisworks exporter must be installed) and post-call guidance ('revit_jobs polls; retry repeats'), plus a hint that overwrite requires a confirm handshake. It never says when to choose this over revit_export or revit_export_view, or when dry_run should be used instead of a real export.

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

Deploy Server