ResInsight views

An MCP-enabled agent can apply complete display settings and inspect the returned native image. MCP is the Model Context Protocol for tool access. A configured server exposes view_list, view_apply, view_render, and observation_get for this workflow. A scene version identifies one confirmed set of display settings. Each apply or render request identifies its model revision, stored result, case, view, and scene version. View edits do not change simulator inputs or run a simulator.

Requirements

Enable the launcher's OPM workflow configuration or supply session and view services through a host integration. Use the rebuilt ResInsight application and its matching generated RIPS client. RIPS is the Python client for ResInsight remote calls.

The unmodified released client does not provide all required view capabilities. The developer guide lists the required native APIs. The session guide describes application connections and process checks.

A trusted application loader must bind the loaded case to its stored result before view operations. The public result_load and result_rebind operations verify source files and native values before issuing these bindings. The result guide explains their exact identity and geometry checks.

Agent workflow

Call project_inspect with the explicit session identifier. Select optional wells from the returned object references. Call view_list with a current loaded-result binding to find its associated views, cameras, display scales, and scene versions. The operation verifies the current project and result binding without applying display changes. Use that result, model revision, and one returned view to construct complete settings. Send complete settings to view_apply and inspect its returned image and edit receipt. For a visual comparison, keep the legend bounds fixed while changing the report time or camera.

Use the returned observation context with view_render to capture the same scene again. Use observation_get to retrieve an existing observation that still represents the current native scene. These operations inspect and change the display of an existing result. They do not import simulator outputs, create result lineage, or execute a simulation.

Data boundary

ResInsight and the local MCP server execute on the workstation. The configured agent client can use a remote model provider for inference. That client can send prompts, tool results, metadata, and rendered images to its provider. Local application execution does not imply local model inference. Users operate under appropriate data sharing agreements with their configured model provider.

Supported settings

PRESSURE requires a stored FIELD revision and uses psi. SWAT, SGAS, SOIL, and PORO use the dimensionless unit 1. The native case must contain the requested property in its supported result category. The report index, calendar date, and elapsed days must match the native case and stored result. The coordinate metadata must match the stored revision.

The camera uses native display coordinates. Its position and target do not provide a conversion from reservoir coordinates. Perspective cameras require a field of view in degrees. Orthographic cameras require parallel_scale, which equals half the visible vertical extent. Vertical exaggeration controls the native grid Z scale.

Legend bounds use the property's unit. The adapter selects a continuous linear legend without centering its range around zero. The returned context records the actual native legend bounds. Display filters use zero-based, inclusive I, J, and K bounds on the main grid. The collection uses AND, with an explicit include or exclude choice for each range.

selected_wells records resolved well path identities. It does not change well visibility, geometry, or simulator inputs. The selected view must belong to the selected case. Linked views, controlled views, and unsupported native filter states prevent view control.

Apply and render

Use view_apply with a complete ViewUpdateRequest. Use scene version 0 for a view without a confirmed edit in the current service. For later edits, use the version from the last edit receipt. An optional expected_observation_id requires that observation's scene to remain current.

A successful edit advances the scene version once. Its receipt contains the actual native context after the edit. The operation then exports a fresh PNG at the requested dimensions. The service decodes the image and checks its dimensions before saving an observation. It also checks native scene state after export.

Use view_render to capture the current confirmed context without applying settings. Reuse the returned context rather than reconstructing it from an earlier request. observation_get retrieves a saved observation without rendering a new frame. With the view service bound, retrieval also requires the observation's native scene to remain current.

Failures and recovery

A changed native scene makes earlier observations stale. A stale observation cannot serve as proof of the current scene. If only the scene changed, apply complete settings using current references and the latest confirmed scene version.

Reconnecting or replacing the project invalidates object references and trusted case bindings. Use result_rebind with the current project context and exact result identifiers to obtain fresh bindings. Call view_list with each fresh binding to obtain its current views and scene versions.

A rejected request returns a typed failure. invalid_model reports inconsistent requested metadata or filter bounds. unsupported_operation reports unsupported properties, unit systems, or missing native capabilities. busy and lost_connection report native call failures. An uncertain edit has effect unknown, so it must not be treated as an unchanged view.

An image failure after a confirmed edit preserves the successful edit receipt. In that outcome, EditedView.observation contains a failure instead of an image. The service never substitutes an earlier PNG for a failed capture. Make sure that both the edit outcome and observation outcome succeed before using an image as evidence.