@modudraft/mcp 0.15.1 → 0.15.2

package/README.md

@@ -94,9 +94,9 @@ Without it, all diagram tools work as usual. The file tools fall back to your cl
 ### Architecture nodes & edges
 | Tool | Description |
 |---|---|
-| `add_node` | Add a component (compute, database, queue, gateway, etc.). `tool` takes a catalog key or a common name and is resolved to the catalog key (see [Tool names](#tool-names)) |
-| `update_node` | Update label, tool, or archetype (a `tool` name is resolved the same way; the archetype is left alone) |
-| `delete_node` | Remove a node and its connections |
+| `add_node` | Add a component (compute, database, queue, gateway, etc.). `tool` takes a catalog key or a common name and is resolved to the catalog key (see [Tool names](#tool-names)). Optional `runs_on` links the node to a Cloud-tab resource (its id or name; a bad value is refused with the valid names) |
+| `update_node` | Update label, tool, or archetype (a `tool` name is resolved the same way; the archetype is left alone). `runs_on` sets the cloud resource the node runs on; pass an empty string or `null` to clear it |
+| `delete_node` | Remove a node and its connections. Data-flow stages linked to it keep existing; only their `node_id` link is cleared |
 | `add_edge` | Connect two nodes with optional label and protocol |
 | `update_edge` | Update edge label or protocol |
 | `delete_edge` | Remove a connection |
@@ -162,7 +162,7 @@ The old `request_body`, `request_format`, `body`, `body_format` and top-level `r
 |---|---|
 | `add_cloud_resource` | Add a cloud resource (cluster, VPC, service, database, queue, etc.) |
 | `update_cloud_resource` | Rename or change the type of a cloud resource |
-| `delete_cloud_resource` | Remove a cloud resource |
+| `delete_cloud_resource` | Remove a cloud resource. Nodes that ran on it (or a child) keep existing; only their `runs_on` link is cleared |
 
 ### Network diagram
 | Tool | Description |
@@ -174,8 +174,8 @@ The old `request_body`, `request_format`, `body`, `body_format` and top-level `r
 ### Data flow diagram
 | Tool | Description |
 |---|---|
-| `add_data_flow_stage` | Add a pipeline stage (source, transform, sink, etc.) |
-| `update_data_flow_stage` | Rename or change the type of a data flow stage |
+| `add_data_flow_stage` | Add a pipeline stage (source, transform, sink, etc.). Optional `node_id` links it to an Architecture-tab node (its id or label; a bad value is refused with the valid names) |
+| `update_data_flow_stage` | Rename or change the type of a data flow stage, or set its `node_id` link (empty string or `null` clears it) |
 | `delete_data_flow_stage` | Remove a data flow stage |
 | `reorder_data_flow_stages` | Set the order of all stages in a data flow diagram |