remove_tank
Remove a storage tank and all attached pipes, with engine validation ensuring the edited network still parses and solves.
Instructions
Remove a storage tank and every pipe attached to it (the inverse of add_tank). The edit is validated against the EPANET engine before it is applied — unique id, the edited model must re-parse with the tank and its connector pipes gone, node count must decrease by exactly one and link count by exactly the removed pipes, and a previously-solvable network must still solve. If controls or rules reference the tank, the engine rejects the edit (fail-closed) rather than leaving a dangling reference.
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": {
"networkId": "<networkId>",
"tankId": "<tankId>"
},
"name": "remove_tank"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tankId | Yes | Id of the tank to remove (use get_nodes to list tank ids). Removing a tank also removes every pipe attached to it. The edit is validated against the EPANET engine before it is applied — the edited model must re-parse with the tank and its pipes gone, node/link counts must decrease by exactly the removed assets, and a previously-solvable network must still solve. If controls or rules reference the tank, the engine rejects the edit (fail-closed) rather than leaving a dangling reference. | |
| networkId | Yes | The network id returned by load_network. |