@rui.branco/revit-mcp 1.0.0 → 1.0.2

package/PRIVACY.md

@@ -0,0 +1,95 @@
+# Privacy Policy
+
+**Effective date:** 21 September 2026
+**Applies to:** the `revit-mcp` MCP server and its bundled Revit bridge add-in
+(the "Software"), distributed as the npm package `@rui.branco/revit-mcp` and as
+the Claude Desktop extension `revit-mcp.mcpb`.
+
+## Summary
+
+The Software runs entirely on your own computer. It has no backend, no account,
+no telemetry and no analytics. It sends nothing to the author, and it does not
+transmit your data anywhere over the internet.
+
+## Data collection
+
+**The author collects no data whatsoever.** The Software contains no telemetry,
+crash reporting, usage analytics, update check or licence check. No personal
+information, model content, file path or identifier is transmitted to the author
+or to any third party operated by the author.
+
+## What the Software processes, and where
+
+The Software reads and edits the Revit model open on your machine. That data is
+processed locally and in memory:
+
+- The Node MCP server exchanges JSON with the bridge add-in strictly over
+  loopback HTTP at `http://127.0.0.1:48884`. The listener binds the `127.0.0.1`
+  literal, not a wildcard, so it is not reachable from your network.
+- The bridge add-in runs inside `Revit.exe` and calls the Revit API directly.
+- Model data leaves your machine only if your MCP client sends it onward. When
+  the client is Claude, your prompts and the tool results the model sees are
+  handled under **Anthropic's** privacy policy, not this one:
+  <https://www.anthropic.com/legal/privacy>
+
+Choosing what to ask Claude, and therefore what model content is included in a
+conversation, is yours to control.
+
+## Local storage on your machine
+
+The Software writes only these, all locally, and never transmits them:
+
+| What | Where | Why |
+| --- | --- | --- |
+| Bridge log | `%LOCALAPPDATA%\RevitMcpBridge\bridge.log` | Diagnosing failures. May contain Revit element ids, view and sheet names, and error text. |
+| Bridge add-in files | `%APPDATA%\Autodesk\Revit\Addins\<version>\` | The installed add-in and its `.addin` manifest. |
+| Diagnostics buffer | In memory, inside Revit | The last 200 dismissed dialogs and resolved warnings. Lost when Revit closes. |
+| Exports you request | The path you specify | Images and PDFs the Software writes only when a tool is called with that path. |
+
+Delete the log file at any time; the Software recreates it only when it next
+logs. Uninstalling the bridge (`revit_uninstall_bridge`) removes the add-in
+files.
+
+## Third-party sharing
+
+**None.** The author does not share, sell, rent or disclose any data, because the
+author never receives any.
+
+The Software makes no outbound internet request of its own. Network activity you
+may observe around it comes from other parties under their own policies: your MCP
+client contacting its provider, and `npm`/`npx` downloading the package from
+<https://registry.npmjs.org> at install time.
+
+## Data retention
+
+The author retains nothing, having received nothing. Local files listed above
+stay on your machine until you delete them or uninstall the Software. The
+in-memory diagnostics buffer holds at most 200 entries and is discarded when
+Revit closes.
+
+## Children
+
+The Software is a professional tool for Autodesk Revit and is not directed at
+children under 13.
+
+## Security
+
+The bridge add-in exposes an **unauthenticated** loopback HTTP listener with full
+Revit API access while Revit is running: any local process on your machine can
+reach it. The add-in is not code-signed. Review the
+[Security](README.md#security) section of the README before installing on a
+shared or untrusted machine.
+
+## Changes to this policy
+
+Material changes will be published in this file, with the effective date above
+updated, and will appear in the repository's commit history:
+<https://github.com/rui-branco/revit-mcp/commits/main/PRIVACY.md>
+
+## Contact
+
+Questions, or a privacy or security concern:
+
+- Issues: <https://github.com/rui-branco/revit-mcp/issues>
+- Private security reports:
+  <https://github.com/rui-branco/revit-mcp/security/advisories/new>

package/README.md

@@ -10,72 +10,77 @@
 it, and produce a full drawing set in plain language — levels and elements,
 sheets and schedules, views and PDF exports.
 
-**Windows · Revit 2025, 2026 or 2027 · Node.js 18+.** The Revit add-in ships
-precompiled, so there is nothing to build and no .NET SDK to install. `npm` is
-never run at startup — the Desktop extension carries its dependencies, and the
-Claude Code route fetches the package once via `npx`.
+**Windows · Revit 2025, 2026 or 2027.** The add-in ships precompiled — nothing
+to build, no .NET SDK. The Claude Desktop extension needs no Node.js either; the
+Claude Code route uses `npx`, so it wants Node 18+.
 
 ## Installation
 
 ### 1. Register the server
 
-#### Claude Desktop — extension
+Two commands, in **Claude Code or Claude Desktop** — same plugin, either app:
 
-1. **[⬇ Download `revit-mcp.mcpb`](https://github.com/rui-branco/revit-mcp/releases/latest/download/revit-mcp.mcpb)**
-2. In Claude Desktop, open **Settings → Extensions**
-3. **Drag the `.mcpb` file onto that window**, then press **Install**
-
-No JSON to edit and nothing to download at runtime: the extension carries the
-server, its dependencies and the Revit add-in. Bridge URL and request timeout
-are exposed as settings under **Settings → Extensions → Revit**.
+```
+/plugin marketplace add rui-branco/revit-mcp
+/plugin install revit@revit-tools
+```
 
-> Double-clicking the file only works if Claude Desktop has registered the
-> `.mcpb` file type; on many installs it has not, so use the drag-and-drop step
-> above.
+That is the whole step. The plugin updates itself from this repo, so there is
+nothing to re-download when a new version ships; `/plugin update` pulls it
+early if you do not want to wait.
 
 <details>
-<summary>Or configure it by hand</summary>
+<summary><b>Other ways to install</b></summary>
+
+These exist for completeness. The plugin above is the supported path, and the
+only one that updates on its own.
+
+**Claude Code, without the plugin**
+
+```bash
+claude mcp add revit --scope user -- npx -y @rui.branco/revit-mcp
+```
+
+`--scope user` enables it in every project; `--scope project` writes it to the
+repo's `.mcp.json` instead, to share with a team.
+
+**Claude Desktop, as a Desktop Extension (.mcpb)**
 
-Open **Settings → Developer → Edit Config** (that is
-`%APPDATA%\Claude\claude_desktop_config.json`) and add the `revit` entry,
-keeping any servers already there:
+[Download `revit-mcp.mcpb`](https://github.com/rui-branco/revit-mcp/releases/latest/download/revit-mcp.mcpb),
+then **Settings → Extensions → Advanced settings → Install extension…** and
+pick the file. It bundles the server, its dependencies and the Revit add-in,
+and runs on Claude Desktop's built-in Node runtime, so neither Node.js nor npm
+is needed. **A sideloaded extension never auto-updates** — every new version
+means downloading and installing the file again, which is why the plugin is
+preferred.
+
+**Claude Desktop, by hand**
+
+**Settings → Developer → Edit Config** opens
+`%APPDATA%\Claude\claude_desktop_config.json`. Add the `revit` entry, keeping
+any servers already there:
 
 ```json
 {
   "mcpServers": {
     "revit": {
       "command": "npx",
-      "args": ["-y", "github:rui-branco/revit-mcp"]
+      "args": ["-y", "@rui.branco/revit-mcp"]
     }
   }
 }
 ```
 
-Then **quit Claude Desktop from the system tray** — closing the window is not
-enough — and reopen it.
-
-If the server shows as failed, Claude Desktop could not find `npx` on its
-`PATH`. Use absolute paths instead (`where.exe npx.cmd` prints yours), or point
-`command` at your `node.exe` with `args` of
-`["C:\\path\\to\\revit-mcp\\index.js"]`.
-
-</details>
-
-#### Claude Code — one command
-
-```bash
-claude mcp add revit --scope user -- npx -y github:rui-branco/revit-mcp
-```
-
-`--scope user` enables it in every project; `--scope project` writes it to the
-repo's `.mcp.json` instead, to share with a team. Check it with `claude mcp list`.
+Then quit Claude Desktop from the system tray — closing the window is not
+enough — and reopen it. If the server shows as failed, Claude Desktop could not
+find `npx` on its `PATH`: use an absolute path (`where.exe npx.cmd` prints
+yours).
 
-<details>
-<summary><b>Other MCP clients</b></summary>
+**Any other MCP client**
 
-Any stdio MCP client works. Use `npx -y github:rui-branco/revit-mcp` as the
-server command; it takes no arguments and needs no environment beyond the
-optional [configuration](#configuration).
+Run `npx -y @rui.branco/revit-mcp` as the server command. It takes no
+arguments and needs no environment beyond the optional
+[configuration](#configuration).
 
 </details>
 
@@ -427,6 +432,24 @@ until the dialog is answered by hand.
 | `did not answer within Nms` | Revit is busy or showing a modal dialog. | Check `revit_diagnostics` — a dialog seen but unanswered is recorded with `answered: false`. Otherwise clear the screen in Revit and retry, or raise `REVIT_MCP_TIMEOUT`. A timed-out write may still have completed. |
 | `no active document` | Revit is on the start page or between documents. | Open a model and retry. `revit_status` deliberately tolerates this, which distinguishes it from the others. |
 
+## Privacy Policy
+
+**This software collects no data.** It has no backend, no account, no telemetry
+and no analytics, and it makes no outbound internet request of its own. Model
+data is processed locally, in memory, and over loopback only.
+
+Model content leaves your machine only if your MCP client sends it onward —
+when that client is Claude, under [Anthropic's privacy
+policy](https://www.anthropic.com/legal/privacy), not this one.
+
+Written locally and never transmitted: the bridge log at
+`%LOCALAPPDATA%\RevitMcpBridge\bridge.log`, the add-in under
+`%APPDATA%\Autodesk\Revit\Addins\`, an in-memory 200-entry diagnostics buffer,
+and any image or PDF you ask a tool to export.
+
+Full policy — collection, storage, third-party sharing, retention and contact:
+**[PRIVACY.md](PRIVACY.md)**.
+
 ## Security
 
 - The add-in runs **inside `Revit.exe` with full Revit API access**. It can

package/lib/tools/detail.js

@@ -37,6 +37,7 @@ export function registerDetailTools(server, bridge) {
         .optional()
         .describe("Line style name, e.g. 'Thin Lines'. Unknown names fall back to the default and are reported."),
     },
+    { title: "Draw Detail Lines", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, lines, line_style }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge
@@ -74,6 +75,7 @@ export function registerDetailTools(server, bridge) {
         .min(1)
         .describe("Notes to place, all in this one call"),
     },
+    { title: "Add Text Notes", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, notes }) => {
       try {
         const result = await bridge.call("/detail/text", { viewId: view_id, notes });

package/lib/tools/diagnostics.js

@@ -16,6 +16,7 @@ export function registerDiagnosticsTools(server, bridge) {
     "revit_diagnostics",
     "Read what the bridge suppressed: the Revit dialogs it answered automatically and the transaction warnings it resolved, oldest first, plus whether auto-dismiss is currently on. CHECK THIS AFTER EVERY BATCH OF WRITES. A silently resolved warning usually means Revit changed something you did not ask for — walls joined differently, an element deleted as a side effect of another — and this buffer is the only record of it. An empty dialogs/failures list means the writes went through cleanly.",
     {},
+    { title: "Read Diagnostics", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/diagnostics");
@@ -40,6 +41,7 @@ export function registerDiagnosticsTools(server, bridge) {
         .default(false)
         .describe("Also empty the dialog/warning buffer that revit_diagnostics reads"),
     },
+    { title: "Set Dialog Auto-Dismiss", readOnlyHint: false, destructiveHint: false },
     async ({ enabled, clear }) => {
       try {
         // The tool argument stays snake_case-free and plain, but the bridge

package/lib/tools/document.js

@@ -40,6 +40,7 @@ export function registerDocumentTools(server, bridge) {
           "Rebuild the project in place: DELETES the existing save_path and the Revit backups beside it (House.0001.rvt, House.0002.rvt) and closes it in Revit first if it is open, then builds the project again at that same path. Defaults to false, which fails with FILE_EXISTS instead. A file something else still holds comes back as FILE_LOCKED — nothing is ever built under a different name.",
         ),
     },
+    { title: "New Project", readOnlyHint: false, destructiveHint: true },
     async ({ save_path, template_path, overwrite }) => {
       try {
         // The tool arguments stay snake_case like every other tool's, but the
@@ -69,6 +70,7 @@ export function registerDocumentTools(server, bridge) {
     "revit_save",
     "Save the active document in place. A model that has never been saved has no path to save to and comes back as NOT_SAVEABLE — use revit_save_as for that one.",
     {},
+    { title: "Save Project", readOnlyHint: false, destructiveHint: false },
     async () => {
       try {
         const result = await bridge.call("/document/save");
@@ -94,6 +96,7 @@ export function registerDocumentTools(server, bridge) {
         .default(false)
         .describe("Replace save_path if it already exists. Default false: an existing file fails with FILE_EXISTS."),
     },
+    { title: "Save Project As", readOnlyHint: false, destructiveHint: true },
     async ({ save_path, overwrite }) => {
       try {
         // The tool arguments stay snake_case like every other tool's, but the
@@ -118,6 +121,7 @@ export function registerDocumentTools(server, bridge) {
         .min(1)
         .describe("Full path of the existing .rvt file to open, e.g. 'C:\\\\Projects\\\\House.rvt'"),
     },
+    { title: "Open Project", readOnlyHint: false, destructiveHint: false },
     async ({ path }) => {
       try {
         const result = await bridge.call("/document/open", { path });
@@ -137,6 +141,7 @@ export function registerDocumentTools(server, bridge) {
         .default(false)
         .describe("Save the document before closing it. Default false: unsaved changes are discarded."),
     },
+    { title: "Close Project", readOnlyHint: false, destructiveHint: true },
     async ({ save }) => {
       try {
         const result = await bridge.call("/document/close", { save });

package/lib/tools/documentation.js

@@ -36,6 +36,7 @@ export function registerDocumentationTools(server, bridge) {
         .optional()
         .describe("View ids to read, all in this one call. Use this or view_id, not both."),
     },
+    { title: "Read View Crop", readOnlyHint: true },
     async ({ view_id, view_ids }) => {
       // Checked here rather than in the schema: a raw shape cannot express
       // "one of these two", and a call with neither must not reach Revit.
@@ -92,6 +93,7 @@ export function registerDocumentationTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports the current crop and the box that would be written, and changes nothing. Pass false to apply it.",
         ),
     },
+    { title: "Set View Crop", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, view_ids, model_bounds, dry_run }) => {
       if (view_id === undefined && view_ids === undefined) {
         return {
@@ -154,6 +156,7 @@ export function registerDocumentationTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports canBeHidden and the current isHidden for every id and changes nothing. Pass false to apply it.",
         ),
     },
+    { title: "Hide Elements in View", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, ids, hidden, dry_run }) => {
       try {
         const result = await bridge.call("/views/hide-elements", {
@@ -209,6 +212,7 @@ export function registerDocumentationTools(server, bridge) {
           "False by default: an existing file at any target path fails the whole call with FILE_EXISTS and nothing is exported.",
         ),
     },
+    { title: "Export PDF", readOnlyHint: false, destructiveHint: false },
     async ({ view_ids, sheet_ids, folder, filename, combine, overwrite }) => {
       // Checked here rather than in the schema: a raw shape cannot express
       // "at least one of these two", and an empty export must not reach Revit.
@@ -262,6 +266,7 @@ export function registerDocumentationTools(server, bridge) {
         .default(0)
         .describe("Body rows to skip, for paging through a long schedule"),
     },
+    { title: "Read Schedule Contents", readOnlyHint: true },
     async ({ schedule_id, limit, offset }) => {
       try {
         const result = await bridge.call("/schedules/read", {
@@ -282,6 +287,7 @@ export function registerDocumentationTools(server, bridge) {
     {
       sheet_id: z.number().int().describe("Sheet id from revit_list_sheets"),
     },
+    { title: "Measure Sheet Layout", readOnlyHint: true },
     async ({ sheet_id }) => {
       try {
         const result = await bridge.call("/sheets/layout", { sheetId: sheet_id });
@@ -310,6 +316,7 @@ export function registerDocumentationTools(server, bridge) {
           `Max sheets to return (default ${DEFAULT_QUERY_LIMIT}, hard cap ${MAX_QUERY_LIMIT} — higher values are clamped, not rejected)`,
         ),
     },
+    { title: "Read Browser Organization", readOnlyHint: true },
     async ({ sheet_ids, limit }) => {
       try {
         const result = await bridge.call("/sheets/browser-organization", {
@@ -353,6 +360,7 @@ export function registerDocumentationTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports the current position and moves nothing. Pass false to apply it.",
         ),
     },
+    { title: "Move Viewport on Sheet", readOnlyHint: false, destructiveHint: false },
     async ({ viewport_id, center, label_offset, label_line_length, dry_run }) => {
       try {
         const result = await bridge.call("/sheets/set-viewport-position", {
@@ -389,6 +397,7 @@ export function registerDocumentationTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports the current position and moves nothing. Pass false to apply it.",
         ),
     },
+    { title: "Move Schedule on Sheet", readOnlyHint: false, destructiveHint: false },
     async ({ instance_id, top_left, dry_run }) => {
       try {
         const result = await bridge.call("/sheets/set-schedule-position", {
@@ -489,6 +498,7 @@ export function registerDocumentationTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports the current configuration and changes nothing. Pass false to apply it.",
         ),
     },
+    { title: "Configure Schedule", readOnlyHint: false, destructiveHint: false },
     async ({ schedule_id, itemized, group_by, fields, filters, grand_total, dry_run }) => {
       if (
         itemized === undefined &&

package/lib/tools/geometry.js

@@ -169,6 +169,7 @@ export function registerGeometryTools(server, bridge) {
         .min(1)
         .describe("One element per entry, all in this one call"),
     },
+    { title: "Create Geometry Elements", readOnlyHint: false, destructiveHint: false },
     async ({ category, name, type_name, material_id, material_name, comments, mark, shapes }) => {
       try {
         const result = await bridge.call("/directshape/create", {
@@ -208,6 +209,7 @@ export function registerGeometryTools(server, bridge) {
         .describe("Comments applied to every tree that does not carry its own"),
       mark: z.string().min(1).optional().describe("Mark applied to every tree that does not carry its own"),
     },
+    { title: "Plant Trees", readOnlyHint: false, destructiveHint: false },
     async ({
       points,
       trunk_height,
@@ -271,6 +273,7 @@ export function registerGeometryTools(server, bridge) {
         .describe("Comments applied to every run that does not carry its own"),
       mark: z.string().min(1).optional().describe("Mark applied to every run that does not carry its own"),
     },
+    { title: "Create Pipe Runs", readOnlyHint: false, destructiveHint: false },
     async ({ runs, category, name, type_name, material_id, material_name, comments, mark }) => {
       try {
         const result = await bridge.call("/pipes/create", {
@@ -309,6 +312,7 @@ export function registerGeometryTools(server, bridge) {
         .describe("Comments applied to every head that does not carry its own"),
       mark: z.string().min(1).optional().describe("Mark applied to every head that does not carry its own"),
     },
+    { title: "Place Sprinklers", readOnlyHint: false, destructiveHint: false },
     async ({ points, radius, height, name, type_name, material_id, material_name, comments, mark }) => {
       try {
         const result = await bridge.call("/sprinklers/place", {

package/lib/tools/graphics.js

@@ -23,6 +23,7 @@ export function registerGraphicsTools(server, bridge) {
         .optional()
         .describe("Ids of several views to read in one call. Use this or view_id, not both."),
     },
+    { title: "Read View Graphics", readOnlyHint: true },
     async ({ view_id, view_ids }) => {
       try {
         if (view_id === undefined && view_ids === undefined) {
@@ -82,6 +83,7 @@ export function registerGraphicsTools(server, bridge) {
           "Turn cast shadows on or off. The bridge probes the view first and reports whether it wrote the parameter (verified) or posted Revit's own command (pending and unverified).",
         ),
     },
+    { title: "Set View Graphics", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, view_ids, style, detail_level, shadow_intensity, sunlight_intensity, shadows }) => {
       try {
         if (view_id === undefined && view_ids === undefined) {
@@ -107,6 +109,7 @@ export function registerGraphicsTools(server, bridge) {
     "revit_get_view_graphics_command_status",
     "What became of the last cast-shadows command revit_set_view_graphics posted: when it was posted, whether Revit has been idle since (which is when a posted command actually runs), and a fresh probe of the shadows parameter now, next to the one taken at the moment of posting. 'verified' is true ONLY when the parameter can be read back as an integer and matches what was asked for; when it cannot be read, verified stays false and verifiedBy is null — a posted UI command that nothing can observe is reported as unverified, not as success. Call this after a set-graphics response that said method 'posted-command'.",
     {},
+    { title: "View Graphics Command Status", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/views/graphics-command-status");
@@ -140,6 +143,7 @@ export function registerGraphicsTools(server, bridge) {
           "Exact parameter ids the template should control, from a previous capture's response. Not to be combined with mode.",
         ),
     },
+    { title: "Capture View Template", readOnlyHint: false, destructiveHint: false },
     async ({ source_view_id, name, mode, parameter_ids }) => {
       try {
         const result = await bridge.call("/views/capture-template", {
@@ -179,6 +183,7 @@ export function registerGraphicsTools(server, bridge) {
         .optional()
         .describe("Allow 'assign' to detach a template a view already has. Without it, such a view fails the call instead.",),
     },
+    { title: "Apply View Template", readOnlyHint: false, destructiveHint: false },
     async ({ template_id, view_ids, mode, dry_run, replace }) => {
       try {
         const result = await bridge.call("/views/apply-template", {

package/lib/tools/install.js

@@ -179,6 +179,7 @@ export function registerInstallTools(server, options = {}) {
         .optional()
         .describe("Never build, even in a source checkout with no prebuilt add-in. A no-op for the published package, which always installs its bundled binary without building."),
     },
+    { title: "Install Bridge Add-In", readOnlyHint: false, destructiveHint: false },
     async ({ revit_version, skip_build }) => {
       try {
         const result = await runInstaller(
@@ -196,6 +197,7 @@ export function registerInstallTools(server, options = {}) {
     "revit_uninstall_bridge",
     "Remove the Revit MCP bridge add-in: deletes the .addin manifest and the install folder for every Revit version that has it. Revit does NOT need to be running, but RESTART REVIT afterwards — a running Revit keeps the already-loaded bridge alive until it closes.",
     {},
+    { title: "Uninstall Bridge Add-In", readOnlyHint: false, destructiveHint: true },
     async () => {
       try {
         const result = await runInstaller({ uninstall: true }, options);

package/lib/tools/material-appearance.js

@@ -53,6 +53,7 @@ export function registerMaterialAppearanceTools(server, bridge) {
     "revit_get_material_appearance",
     "Read the appearance asset behind a material — the rendered look, as opposed to the shading colour revit_create_material sets. Read-only: it changes nothing. It reports the material's shading side (colorRgb, transparency, shininess, smoothness, useRenderAppearanceForShading), the AppearanceAssetElement it really points at (id, name and the SCHEMA it was built from, e.g. 'Generic' or 'Ceramic'), and every direct property of that asset: 'name' as the API knows it (e.g. 'generic_diffuse'), 'type' and 'runtimeType', the typed 'value' it holds, and 'patchType' — which of revit_set_material_appearance's five types can write it, or null when none can. Anything connected to a property comes back under 'connected' with the bitmap's file, tile size in feet and rotation. 'sharedWithMaterialIds' is every OTHER material pointing at the same asset: non-empty means editing it in place would repaint them too, which is exactly what revit_set_material_appearance refuses to do. NOTE on 'readOnly': Revit hands the rendering asset out read-only outside an edit scope, so it is usually true for every property and is NOT the test of whether a property can be written — revit_set_material_appearance is, because it validates inside an edit scope. A material with no appearance asset at all is a normal state, not a broken one: it renders from Color and Transparency alone, appearanceAssetId comes back null with an empty property list, and it does NOT need a bitmap — create_generic on revit_set_material_appearance gives it a textureless Generic asset to patch. 'genericAssetAvailable' says up front whether Revit's library can supply one on this machine.",
     MATERIAL,
+    { title: "Read Material Appearance", readOnlyHint: true },
     async ({ material_id, material_name }) => {
       try {
         const result = await bridge.call("/materials/appearance", {
@@ -131,6 +132,7 @@ export function registerMaterialAppearanceTools(server, bridge) {
           "Also write the first patched colour onto the material's own Color, which is what shaded views draw. Needs at least one 'color' patch.",
         ),
     },
+    { title: "Edit Material Appearance", readOnlyHint: false, destructiveHint: false },
     async ({
       material_id,
       material_name,

package/lib/tools/materials.js

@@ -58,6 +58,7 @@ export function registerMaterialTools(server, bridge) {
     "revit_list_materials",
     "List the materials in the document: id, name, colour as {r, g, b}, and the id of its appearance asset when it has one. This is where a material_id comes from — for revit_create_directshape, revit_place_planting, revit_create_pipes, revit_place_sprinklers, revit_assign_material, revit_create_wall_type and revit_create_floor_type. A Revit template usually ships dozens, so check here before creating a new one.",
     {},
+    { title: "List Materials", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/materials", {});
@@ -110,6 +111,7 @@ export function registerMaterialTools(server, bridge) {
           "Full path to a texture bitmap, to make the material textured in this same call. Revit's own library is under C:\\Program Files\\Common Files\\Autodesk Shared\\Materials\\Textures. A file that does not exist is refused before anything is created. Tile size, rotation and tint belong to revit_set_material_texture.",
         ),
     },
+    { title: "Create Material", readOnlyHint: false, destructiveHint: false },
     async ({
       name,
       color,
@@ -168,6 +170,7 @@ export function registerMaterialTools(server, bridge) {
         .optional()
         .describe("Colour multiplied over the bitmap, as {r, g, b}, each channel 0-255"),
     },
+    { title: "Set Material Texture", readOnlyHint: false, destructiveHint: false },
     async ({ material_id, material_name, texture_path, scale, rotation, tint }) => {
       try {
         const result = await bridge.call("/materials/set-texture", {
@@ -192,6 +195,7 @@ export function registerMaterialTools(server, bridge) {
       material_id: z.number().int().describe("Material id from revit_list_materials or revit_create_material"),
       element_ids: z.array(z.number().int()).min(1).describe("Elements to put the material on"),
     },
+    { title: "Assign Material", readOnlyHint: false, destructiveHint: false },
     async ({ material_id, element_ids }) => {
       try {
         const result = await bridge.call("/materials/assign", {
@@ -209,6 +213,7 @@ export function registerMaterialTools(server, bridge) {
     "revit_create_wall_type",
     "Create a wall type carrying a material and a thickness, by duplicating an existing type and giving it a single structural layer. A wall's material is a property of its type, not of the wall, so this is the only way to get walls that are not the template's default grey: create the type, then pass its name to revit_create_walls as wall_type. A type that already exists by this name is REUSED and comes back with created:false and its current thickness and material — it is not re-cut to match the request. Thickness is feet (Revit internal units). One call is one undo step.",
     HOST_TYPE,
+    { title: "Create Wall Type", readOnlyHint: false, destructiveHint: false },
     async ({ name, based_on_type_name, thickness, material_id, material_name }) => {
       try {
         const result = await bridge.call("/walltypes/create", {
@@ -229,6 +234,7 @@ export function registerMaterialTools(server, bridge) {
     "revit_create_floor_type",
     "Create a floor type carrying a material and a thickness, by duplicating an existing type and giving it a single structural layer. Like walls, a floor's material lives on its type — this is how paving stops being grey: create the type, then pass its name to revit_create_floor as type_name. A type that already exists by this name is REUSED and comes back with created:false and its current thickness and material. Thickness is feet (Revit internal units). One call is one undo step.",
     HOST_TYPE,
+    { title: "Create Floor Type", readOnlyHint: false, destructiveHint: false },
     async ({ name, based_on_type_name, thickness, material_id, material_name }) => {
       try {
         const result = await bridge.call("/floortypes/create", {

package/lib/tools/model.js

@@ -43,6 +43,7 @@ export function registerModelTools(server, bridge) {
         .optional()
         .describe("Level the toposolid is hosted on. Omit it to use the lowest level in the document."),
     },
+    { title: "Create Site Surface", readOnlyHint: false, destructiveHint: false },
     async ({ points, type_name, level }) => {
       try {
         const result = await bridge.call("/toposolid/create", {
@@ -72,6 +73,7 @@ export function registerModelTools(server, bridge) {
         .optional()
         .describe("Id of the toposolid to flatten. Only needed when the document has more than one."),
     },
+    { title: "Flatten Site Surface Region", readOnlyHint: false, destructiveHint: true },
     async ({ points, elevation, toposolid_id }) => {
       try {
         const result = await bridge.call("/toposolid/flatten", {
@@ -111,6 +113,7 @@ export function registerModelTools(server, bridge) {
           "Height offset from the level in feet, positive up. Defaults to 0. Written to the floor's 'Height Offset From Level' parameter and read back into the response.",
         ),
     },
+    { title: "Create Floor", readOnlyHint: false, destructiveHint: false },
     async ({ level, boundary, type_name, structural, offset }) => {
       try {
         const result = await bridge.call("/floors/create", {
@@ -138,6 +141,7 @@ export function registerModelTools(server, bridge) {
         .describe("Full paths of .rfa files to load. Pass the whole batch in one call."),
       path: z.string().min(1).optional().describe("A single .rfa path, as a shorthand for paths"),
     },
+    { title: "Load Families", readOnlyHint: false, destructiveHint: false },
     async ({ paths, path }) => {
       try {
         if (!paths && !path) {
@@ -172,6 +176,7 @@ export function registerModelTools(server, bridge) {
           "Family name to filter by, e.g. 'M_RPC Tree - Deciduous'. This is the family, not the type — it returns every type in that family.",
         ),
     },
+    { title: "List Family Types", readOnlyHint: true },
     async ({ category, family_name }) => {
       try {
         const result = await bridge.call("/families/symbols", {
@@ -215,6 +220,7 @@ export function registerModelTools(server, bridge) {
           "Rotation in radians about the vertical axis through each point, counter-clockwise in plan. Radians is Revit's internal angle unit, as feet is its internal length unit.",
         ),
     },
+    { title: "Place Families", readOnlyHint: false, destructiveHint: false },
     async ({ symbol_id, level, points, z: zOffset, rotation }) => {
       try {
         const result = await bridge.call("/families/place", {
@@ -264,6 +270,7 @@ export function registerModelTools(server, bridge) {
           "Height of the sill above the level, in feet. Omit it for 3 feet on a window and Revit's own on anything else.",
         ),
     },
+    { title: "Place Doors and Windows", readOnlyHint: false, destructiveHint: false },
     async ({ symbol_id, points, host_wall_id, level, sill_height }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge

package/lib/tools/parameters.js

@@ -63,6 +63,7 @@ export function registerParameterTools(server, bridge) {
         .optional()
         .describe("True (the default) binds it per element; false binds it to the type, so every element of that type shares one value."),
     },
+    { title: "Create Project Parameter", readOnlyHint: false, destructiveHint: false },
     async ({ name, category, categories, type, group, instance }) => {
       // Checked here rather than in the schema: a raw shape cannot express
       // "one of these two", and a call with neither must not reach Revit.
@@ -120,6 +121,7 @@ export function registerParameterTools(server, bridge) {
         .min(1)
         .describe("Sheet/name/value triples, all in this one call"),
     },
+    { title: "Set Sheet Parameters", readOnlyHint: false, destructiveHint: false },
     async ({ values }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge

package/lib/tools/quality.js

@@ -50,6 +50,7 @@ export function registerQualityTools(server, bridge) {
           "Force vertex/segment lists on or off. Omit it and they come back whenever there are 500 or fewer, and collapse to a count plus a min/max Z above that. true asks for them anyway, capped at 500 with truncated: true.",
         ),
     },
+    { title: "Inspect Elements", readOnlyHint: true },
     async ({ ids, include_parameters, include_geometry }) => {
       try {
         // The tool arguments stay snake_case like every other tool's, but the
@@ -88,6 +89,7 @@ export function registerQualityTools(server, bridge) {
           "true (the default) measures and reports what the move would do without changing the model. Pass false to actually move.",
         ),
     },
+    { title: "Move Elements", readOnlyHint: false, destructiveHint: false },
     async ({ ids, translation, dry_run }) => {
       try {
         const result = await bridge.call("/elements/move", {
@@ -129,6 +131,7 @@ export function registerQualityTools(server, bridge) {
           "true (the default) runs the CanBeExcavatedBy preflight and reports the current volume without changing the model. Pass false to actually excavate.",
         ),
     },
+    { title: "Excavate Site Surface", readOnlyHint: false, destructiveHint: false },
     async ({ toposolid_id, ids, dry_run }) => {
       try {
         const result = await bridge.call("/toposolid/excavate", {
@@ -165,6 +168,7 @@ export function registerQualityTools(server, bridge) {
         .default(0)
         .describe("Warnings to skip, for paging through a noisy model"),
     },
+    { title: "Read Model Warnings", readOnlyHint: true },
     async ({ limit, offset }) => {
       try {
         const result = await bridge.call("/document/warnings", {
@@ -185,6 +189,7 @@ export function registerQualityTools(server, bridge) {
     "revit_list_view_templates",
     "List the view templates in the model: id, name, view type, and the parameters each template CONTROLS with their labels. Read-only. Check this before setting a scale, a display style or a category override on a view — a parameter the template controls is one the view cannot hold its own value for, which is why a setting you wrote reads back as something else.",
     {},
+    { title: "List View Templates", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/views/templates");

package/lib/tools/read.js

@@ -19,6 +19,7 @@ export function registerReadTools(server, bridge) {
     "revit_status",
     "Check whether Revit is reachable: version, active document name/path, and whether the model is workshared. Run this first when any other Revit tool fails.",
     {},
+    { title: "Revit Status", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/status");
@@ -33,6 +34,7 @@ export function registerReadTools(server, bridge) {
     "revit_list_levels",
     "List the levels in the active document: id, name and elevation (Revit internal units, decimal feet).",
     {},
+    { title: "List Levels", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/levels");
@@ -47,6 +49,7 @@ export function registerReadTools(server, bridge) {
     "revit_list_categories",
     "List the categories present in the active document with an element count each. Use this to find the exact category name to pass to revit_query_elements.",
     {},
+    { title: "List Categories", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/categories");
@@ -85,6 +88,7 @@ export function registerReadTools(server, bridge) {
         .default(0)
         .describe("Rows to skip, for paging through a large result"),
     },
+    { title: "Find Elements", readOnlyHint: true },
     async ({ category, level, type_name, limit, offset }) => {
       try {
         // The tool argument stays snake_case like every other tool's, but the
@@ -116,6 +120,7 @@ export function registerReadTools(server, bridge) {
         .optional()
         .describe("Parameter names to read, e.g. ['Comments', 'Mark', 'Unconnected Height']"),
     },
+    { title: "Read Elements", readOnlyHint: true },
     async ({ ids, params }) => {
       try {
         const result = await bridge.call("/elements", { ids, params });
@@ -130,6 +135,7 @@ export function registerReadTools(server, bridge) {
     "revit_get_selection",
     "Read what the user currently has selected in the Revit UI. Use this when the user says 'this wall', 'the selected elements' or similar.",
     {},
+    { title: "Read Current Selection", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/selection");

package/lib/tools/reload.js

@@ -15,6 +15,7 @@ export function registerReloadTools(server, bridge) {
     "revit_reload_bridge",
     "Reload the bridge's endpoint logic from disk without restarting Revit, after rebuilding the add-in. Use this while developing the bridge itself: it swaps the freshly built logic assembly into the running Revit, keeping the open model, the HTTP listener and any queued work alive. The response says whether the previous version was actually unloaded — if unloadedPrevious is false, the new logic IS live but the old one is still in memory, which is worth investigating rather than ignoring. Nothing changes until the DLL on disk changes, so build first.",
     {},
+    { title: "Reload Bridge Logic", readOnlyHint: false, destructiveHint: false },
     async () => {
       try {
         const result = await bridge.call("/reload");

package/lib/tools/sheet-collections.js

@@ -10,6 +10,7 @@ export function registerSheetCollectionTools(server, bridge) {
     "revit_list_sheet_collections",
     "List the sheet collections in the active document — the collapsible groups Revit draws under Sheets in the Project Browser — with each collection's id, name and member sheets (id, number, name). 'unassignedSheets' is every sheet in no collection. Read-only.",
     {},
+    { title: "List Sheet Collections", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/sheets/collections");
@@ -46,6 +47,7 @@ export function registerSheetCollectionTools(server, bridge) {
         .optional()
         .describe("Defaults to true: report the plan without writing. Pass false to apply it."),
     },
+    { title: "Group Sheets into Collections", readOnlyHint: false, destructiveHint: false },
     async ({ collections, dry_run }) => {
       try {
         // Tool arguments stay snake_case; the bridge reads sheetIds / dryRun.

package/lib/tools/sheets.js

@@ -11,6 +11,7 @@ export function registerSheetTools(server, bridge) {
     "revit_list_titleblocks",
     "List the title block family types loaded in the active document: id, family name and type name. Call this before revit_create_sheets — every sheet needs a title block, and this is where its id comes from. An empty list means no title block family is loaded, so sheets cannot be created yet.",
     {},
+    { title: "List Title Blocks", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/titleblocks");
@@ -25,6 +26,7 @@ export function registerSheetTools(server, bridge) {
     "revit_list_sheets",
     "List the sheets in the active document: id, sheet number and name, ordered by sheet number.",
     {},
+    { title: "List Sheets", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/sheets");
@@ -59,6 +61,7 @@ export function registerSheetTools(server, bridge) {
           "Title block family type id from revit_list_titleblocks. Omit it to use the first one loaded.",
         ),
     },
+    { title: "Create Sheets", readOnlyHint: false, destructiveHint: false },
     async ({ sheets, title_block_id }) => {
       try {
         // The tool argument stays snake_case like every other tool's, but the

package/lib/tools/titleblocks.js

@@ -32,6 +32,7 @@ export function registerTitleblockTools(server, bridge) {
         .int()
         .describe("Id of the loaded title block TYPE (a FamilySymbol), from revit_list_titleblocks"),
     },
+    { title: "Inspect Title Block Family", readOnlyHint: true },
     async ({ symbol_id }) => {
       try {
         // Tool arguments stay snake_case; the bridge reads symbolId.
@@ -119,6 +120,7 @@ export function registerTitleblockTools(server, bridge) {
           "DEFAULTS TO TRUE. True resolves every id and text type and reports what it would do, changing nothing. Pass false to apply it and load the family back.",
         ),
     },
+    { title: "Edit Title Block Family", readOnlyHint: false, destructiveHint: true },
     async ({
       symbol_id,
       expected_family_name,

package/lib/tools/views.js

@@ -21,6 +21,7 @@ export function registerViewTools(server, bridge) {
     "revit_list_views",
     "List the non-template views in the document: id, name, view type, and whether each is already placed on a sheet. A view with a frame also carries viewDirection, rightDirection and upDirection as {x,y,z} — viewDirection is Revit's direction towards the VIEWER, so a section looking north reports {x:0,y:-1,z:0}. Sheets themselves are not listed — use revit_list_sheets for those. A view that is already on a sheet cannot be placed on another one; duplicate it first with revit_duplicate_view.",
     {},
+    { title: "List Views", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/views");
@@ -51,6 +52,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("View scale denominator, e.g. 100 for 1:100. Omit it to keep the type's default."),
     },
+    { title: "Create Plan View", readOnlyHint: false, destructiveHint: false },
     async ({ level, name, view_family_type, scale }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge
@@ -80,6 +82,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("View scale denominator, e.g. 20 for 1:20. Omit it to keep the type's default."),
     },
+    { title: "Create Drafting View", readOnlyHint: false, destructiveHint: false },
     async ({ name, scale }) => {
       try {
         const result = await bridge.call("/views/create-drafting", { name, scale });
@@ -122,6 +125,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("View scale denominator, e.g. 50 for 1:50. Omit it to keep the type's default."),
     },
+    { title: "Create Section View", readOnlyHint: false, destructiveHint: false },
     async ({ name, origin, direction, width, height, depth, scale }) => {
       try {
         const result = await bridge.call("/views/create-section", {
@@ -144,6 +148,7 @@ export function registerViewTools(server, bridge) {
     "revit_list_legends",
     "List the legend views in the document: id, name and scale. Read-only, and that is the point — Revit's API cannot author the first legend in a document, so this is the set revit_create_legend has to duplicate from. An empty list means a legend has to be made once in the Revit UI (View tab > Legends > Legend), or come from the template, before any legend can be created from here.",
     {},
+    { title: "List Legends", readOnlyHint: true },
     async () => {
       try {
         const result = await bridge.call("/views/legends");
@@ -171,6 +176,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("View scale denominator, e.g. 50 for 1:50. Omit it to keep the source legend's scale."),
     },
+    { title: "Create Legend", readOnlyHint: false, destructiveHint: false },
     async ({ name, from_legend_id, scale }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge
@@ -211,6 +217,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("View scale denominator, e.g. 100 for 1:100. Ignored on a perspective view."),
     },
+    { title: "Create 3D View", readOnlyHint: false, destructiveHint: false },
     async ({ name, eye, target, perspective, scale }) => {
       try {
         const result = await bridge.call("/views/create-3d", {
@@ -250,6 +257,7 @@ export function registerViewTools(server, bridge) {
           "Not handled here. Send it to revit_set_view_graphics, which probes whether the shadows parameter is writable on that view and says which route it took. Passing it here fails the call rather than silently doing nothing.",
         ),
     },
+    { title: "Set View Display Style", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, style, detail_level, shadows }) => {
       try {
         const result = await bridge.call("/views/set-style", {
@@ -295,6 +303,7 @@ export function registerViewTools(server, bridge) {
           "Full path of the backdrop image, required with kind 'image'. Revit reads it off disk every time it draws the view, so the file has to stay there.",
         ),
     },
+    { title: "Set View Background", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, kind, sky_color, horizon_color, ground_color, image_path }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge
@@ -330,6 +339,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("True (the default) hides them; false brings them back."),
     },
+    { title: "Hide Categories in View", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, categories, hidden }) => {
       try {
         const result = await bridge.call("/views/hide-categories", {
@@ -398,6 +408,7 @@ export function registerViewTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports each category's current override and the merged override that would be written, and changes nothing. Pass false to apply it.",
         ),
     },
+    { title: "Override Category Graphics", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, overrides, dry_run }) => {
       const rows = overrides.map((row) => ({
         category: row.category,
@@ -471,6 +482,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("Time as HH:MM on a 24-hour clock, e.g. '15:30'. Puts the view in Still Image mode. Not to be combined with azimuth/altitude."),
     },
+    { title: "Set View Sun Position", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, azimuth, altitude, date, time }) => {
       // Checked here rather than in the schema: a raw shape cannot express
       // "one of these two groups", and a call with neither must not reach Revit.
@@ -540,6 +552,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("PNG (the default), JPEG, JPEGLossless, JPEGMedium, JPEGSmallest, BMP, TIFF or TARGA"),
     },
+    { title: "Export View Image", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, view_ids, path, width, height, format }) => {
       try {
         if (view_id === undefined && !view_ids) {
@@ -573,6 +586,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("Revit's ViewDuplicateOption. Defaults to Duplicate."),
     },
+    { title: "Duplicate View", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, name, detailing }) => {
       try {
         const result = await bridge.call("/views/duplicate", {
@@ -607,6 +621,7 @@ export function registerViewTools(server, bridge) {
         .positive()
         .describe("View scale denominator, e.g. 100 for 1:100. Revit's range is 1 to 24000."),
     },
+    { title: "Set View Scale", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, view_ids, scale }) => {
       // Checked here rather than in the schema: a raw shape cannot express
       // "one of these two", and a call with neither must not reach Revit.
@@ -659,6 +674,7 @@ export function registerViewTools(server, bridge) {
           "DEFAULTS TO TRUE. True reports the view's current size and the multiplier asked for, and changes nothing. Pass false to apply it.",
         ),
     },
+    { title: "Resize Perspective View", readOnlyHint: false, destructiveHint: false },
     async ({ view_id, multiplier, dry_run }) => {
       try {
         const result = await bridge.call("/views/scale-perspective-crop", {
@@ -695,6 +711,7 @@ export function registerViewTools(server, bridge) {
         .min(1)
         .describe("Placements to make, all in this one call"),
     },
+    { title: "Place Views on Sheets", readOnlyHint: false, destructiveHint: false },
     async ({ placements }) => {
       try {
         // The tool arguments stay snake_case like every other tool's; the bridge
@@ -734,6 +751,7 @@ export function registerViewTools(server, bridge) {
         .optional()
         .describe("View scale denominator. Schedules have no meaningful scale; omit it unless you know otherwise."),
     },
+    { title: "Create Schedule", readOnlyHint: false, destructiveHint: false },
     async ({ category, name, fields, scale }) => {
       try {
         const result = await bridge.call("/schedules/create", { category, name, fields, scale });

package/lib/tools/write.js

@@ -22,6 +22,7 @@ export function registerWriteTools(server, bridge) {
         .min(1)
         .describe("Levels to create"),
     },
+    { title: "Create Levels", readOnlyHint: false, destructiveHint: false },
     async ({ levels }) => {
       try {
         const result = await bridge.call("/levels/create", { levels });
@@ -52,6 +53,7 @@ export function registerWriteTools(server, bridge) {
         .min(1)
         .describe("Wall centrelines in plan, in feet. One wall per curve."),
     },
+    { title: "Create Walls", readOnlyHint: false, destructiveHint: false },
     async ({ level, wall_type, height, curves }) => {
       try {
         // The tool argument stays snake_case like every other tool's, but the
@@ -86,6 +88,7 @@ export function registerWriteTools(server, bridge) {
           "Revit's own parameter id, for when the name matches more than one: negative for a built-in (e.g. -1002062 SCHEDULE_LEVEL_PARAM), positive for a shared or project parameter. Must be a parameter of the name given. Only needed when the name is ambiguous.",
         ),
     },
+    { title: "Set Parameters", readOnlyHint: false, destructiveHint: false },
     async ({ ids, name, value, parameter_id }) => {
       try {
         // Left out entirely when it was not given: the bridge only asks which
@@ -110,6 +113,7 @@ export function registerWriteTools(server, bridge) {
     {
       ids: z.array(z.number().int()).min(1).describe("Element ids to delete"),
     },
+    { title: "Delete Elements", readOnlyHint: false, destructiveHint: true },
     async ({ ids }) => {
       try {
         const result = await bridge.call("/elements/delete", { ids });

package/manifest.json

@@ -2,7 +2,7 @@
   "manifest_version": "0.2",
   "name": "revit-mcp",
   "display_name": "Revit",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Query and edit the Autodesk Revit model open on your desktop.",
   "long_description": "Connects Claude to the Revit model currently open on this Windows machine through a bundled C# bridge add-in. Query levels and elements, read and write parameters, model geometry, and produce a full drawing set: sheets, views, schedules and PDF exports. Requires Autodesk Revit 2025, 2026 or 2027, and a one-time bridge install run from inside Claude.",
   "author": {
@@ -412,5 +412,8 @@
     "runtimes": {
       "node": ">=18.0.0"
     }
-  }
+  },
+  "privacy_policies": [
+    "https://github.com/rui-branco/revit-mcp/blob/main/PRIVACY.md"
+  ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rui.branco/revit-mcp",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "MCP server for Autodesk Revit: read and edit the open model from an MCP client, via a bundled C# bridge add-in that runs inside Revit",
   "keywords": [
     "revit",
@@ -32,7 +32,8 @@
     "revit-bridge/dist/",
     "README.md",
     "LICENSE",
-    "manifest.json"
+    "manifest.json",
+    "PRIVACY.md"
   ],
   "engines": {
     "node": ">=18"