Instrument Method Profiles

Save reusable method settings exposed by an installed driver, such as a supported pipetting height. These Profiles are separate from workstation selection and layout configurations.

Inspect the available methods

Read this configuration's instrument Profile catalogue. Show the available modules, method parameters, defaults and limits. Do not save or change anything.

The catalogue comes from the driver. A registered MCP tool does not guarantee that the connected driver supplies methods. Use the actual module and method identifiers returned by the catalogue.

Review and save

Ask the agent to validate proposed parameters first and explain any experimental implications. After approving the exact settings, save a new Profile or update an existing one against its current revision. Read back the saved revision.

Operation-specific Profiles can restrict allowed source, destination and tip models, per-aspiration volume and required source conditions. Editing requires the complete intended parameters and applicability. A saved revision is a software record, not a calibrated or scientifically validated method.

Use an exact revision in a supported run

Saving does not change every run. Inspect the program snapshot's execution steps, review where the method is intended, then explicitly bind a Profile revision to those steps when starting or submitting a run. The OS captures the selected revision for the admitted run; later Profile edits do not change it.

Execution support is limited to implemented driver paths. In 0.2.0 the Hamilton adapter supports scoped pipetting selections on specified batch paths; unsupported paths and shared-setting changes are rejected. New Profile parameter combinations still require matching vendor simulation and equipment qualification. The default Opentrons package does not acquire Hamilton support by saving a Profile.

After execution, inspect the recorded Profile references, supplied parameters and effective driver settings. Do not infer application merely because a save succeeded.

This task currently documents the AI route through the MCP Profile tools; no unverified interface editing route is assumed.