List available ProSuite quality conditions.

Returns condition names and their one-line description. Use search to filter by keyword (matched against name and description). Pass a result name to describe_condition to get full parameter details before building a run_verification call.

Describe the parameters of a ProSuite quality condition.

Returns the full docstring and parameter list with types. Dataset parameters expect a dataset name string (must match a name in the datasets list you will pass to run_verification). Primitive parameters take their direct value (number, bool, string).

Describe the loaded QA spec file: available specifications, workspace definitions, and per-specification summary of conditions, workspace IDs, and dataset names.

Call this before run_xml_verification to learn:

• Which specification_name values exist in the spec (pass one to run_xml_verification)

• Which workspace_id values need to be replaced with real paths

• Which datasets each specification expects (useful for sanity-checking the workspace)

Requires PROSUITE_SPEC_PATH to be configured.

Search the loaded QA spec for conditions matching a natural-language query.

Returns up to max_results conditions whose name, description, or category contains the query string (case-insensitive). Claude bridges any language gap — queries in English, German, French, or Italian all work.

Each result includes:

• name: the full condition name (human-readable rule statement)

• category: domain grouping from the spec

• allow_errors: False means a hard failure, True means tolerated

• condition_request: ready to pass directly into run_verification's conditions list (includes condition method name and pre-filled params)

• required_datasets: dataset names and filter expressions to include in run_verification's datasets list

Requires PROSUITE_SPEC_PATH to be configured. Returns an error dict if no spec is loaded.

Load a .qa.xml spec file at runtime.

Replaces any previously loaded spec so that subsequent search_spec calls use the new file. Use this when the spec path is only known at conversation time (e.g. a file on OneDrive or a network share) instead of pre-configuring PROSUITE_SPEC_PATH.

Args: path: Absolute path to the .qa.xml spec file on the local machine.

Returns a dict with 'conditions_loaded' on success, or 'error' on failure.

Run a ProSuite quality verification.

Build an ad-hoc condition-list specification and run it against the given workspace. The ProSuite service (prosuite-qa-microservice) must be reachable at the host/port configured via PROSUITE_HOST / PROSUITE_PORT environment variables (default: localhost:5151).

Args: model_catalog_path: Workspace path on the server, e.g. 'C:/data/mydb.gdb' or a .sde connection file. model_name: Logical name for the data model (arbitrary, used in generated condition names). datasets: Feature classes or tables to make available for conditions. Each entry has a 'name' (feature class name) and an optional 'filter_expression' (SQL WHERE clause). conditions: Conditions to run. Each entry has: - condition: method name from list_conditions (e.g. 'qa_min_length_0') - params: dict mapping parameter names to values. Dataset parameters take a string matching a name in 'datasets'; primitive parameters take their direct value. output_dir: Optional server-side directory for Issues.gdb and HTML report. The service process must have write access. envelope: Optional spatial filter {x_min, y_min, x_max, y_max}. Omit for full-extent verification.

Returns a summary with status, total_errors, and per-condition breakdown. Check 'status': 'error' for connection or parameter failures.

Run a ProSuite quality verification directly from the loaded XML spec file.

Unlike run_verification, this tool sends the XML spec to the ProSuite service as-is, without decomposing it into individual conditions and datasets. This preserves per-condition dataset filters, default scalar values, and all other spec details exactly as configured.

Use search_spec (with empty query) to discover available specification_name values and workspace_id keys that need to be replaced.

Args: specification_name: Name of the QualitySpecification element inside the XML file to run (e.g. 'Copy of DATA_OSM_10_Demo'). data_source_replacements: Maps each workspace_id in the XML to the actual workspace path on the ProSuite server. Example: [{"workspace_id": "DATA_OSM", "workspace_path": "C:/data/osm.sde"}] output_dir: Optional server-side directory for Issues.gdb and HTML report. envelope: Optional spatial filter {x_min, y_min, x_max, y_max}.

Returns a summary with status, total_errors, and per-condition breakdown. Requires PROSUITE_SPEC_PATH to be configured.