Built-in MCP Tools - Revision history

Ollvihe: /* Overview */

2026-08-13T12:53:11Z

Overview

← Older revision		Revision as of 12:53, 13 August 2026
Line 2:		Line 2:

	== Overview==		== Overview==
	The built-in tools are always available in the MCP interface. All three tools are ~~'''~~read-only~~'''~~: they only retrieve data and never modify models, data tables, or any other server-side state. In MCP terms, each tool is annotated with readOnlyHint: true and destructiveHint: false. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.		The built-in tools are always available in the MCP interface. All three tools are read-only: they only retrieve data and never modify models, data tables, or any other server-side state. In MCP terms, each tool is annotated with readOnlyHint: true and destructiveHint: false. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.

	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

Ollvihe at 12:52, 13 August 2026

2026-08-13T12:52:55Z

← Older revision		Revision as of 12:52, 13 August 2026
Line 1:		Line 1:
	QPR ProcessAnalyzer ships with the followin built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them. The built-in tools are always available in the MCP interface. All three tools are '''read-only''': they only retrieve data and never modify models, data tables, or any other server-side state. In MCP terms, each tool is annotated with readOnlyHint: true and destructiveHint: false. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.		QPR ProcessAnalyzer ships with the followin built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them.

			== Overview==
			The built-in tools are always available in the MCP interface. All three tools are '''read-only''': they only retrieve data and never modify models, data tables, or any other server-side state. In MCP terms, each tool is annotated with readOnlyHint: true and destructiveHint: false. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.

	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]].		The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]].

	~~= QPR ProcessAnalyzer Built-in MCP Tools =~~
	QPR ProcessAnalyzer ships with three built-in MCP (Model Context Protocol) tools that allow an MCP client to explore process models and run analytical queries against them. All three tools are '''read-only''': they only retrieve data and never modify models, data tables, or any other server-side state. In MCP terms, each tool is annotated with readOnlyHint: true and destructiveHint: false.

	A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (data tables, columns, object types), and finally use '''Generic Query''' to compute results.		A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (data tables, columns, object types), and finally use '''Generic Query''' to compute results.

	== List Available Process Models ==		== Tools==
			=== List Available Process Models ===
	Lists all process models that are available on the server. For each model it reports basic metadata such as the model ID, name, and description, whether the model uses in-memory processing, and whether it is object-centric (OCPM/OCEL) or case-centric. This tool is read-only.		Lists all process models that are available on the server. For each model it reports basic metadata such as the model ID, name, and description, whether the model uses in-memory processing, and whether it is object-centric (OCPM/OCEL) or case-centric. This tool is read-only.

Line 17:		Line 18:
	'''Outputs.''' The tool returns an object with a single models property, which is an array of model objects. Each model object contains a unique id (integer), a name and description (strings), an isInMemoryModel flag that is true only when the model uses in-memory processing, and an isObjectCentric flag that is true for object-centric (OCPM/OCEL) models and false for case-centric ones. Each object also includes audit information: createdDate and modifiedDate (ISO date-time strings) together with createdBy and modifiedBy (the names of the users who created and last modified the model). Only models that pass a validity check are included in the result.		'''Outputs.''' The tool returns an object with a single models property, which is an array of model objects. Each model object contains a unique id (integer), a name and description (strings), an isInMemoryModel flag that is true only when the model uses in-memory processing, and an isObjectCentric flag that is true for object-centric (OCPM/OCEL) models and false for case-centric ones. Each object also includes audit information: createdDate and modifiedDate (ISO date-time strings) together with createdBy and modifiedBy (the names of the users who created and last modified the model). Only models that pass a validity check are included in the result.

	== Get Model Details ==		=== Get Model Details ===
	Returns detailed information about a single model, identified by its ID. In addition to the basic metadata also returned by '''List Available Process Models''', this tool exposes the model's configuration and the data tables it uses, including their columns, data types, primary keys, and foreign keys. This is the recommended way to discover the exact table and column names needed to build a query. This tool is read-only.		Returns detailed information about a single model, identified by its ID. In addition to the basic metadata also returned by '''List Available Process Models''', this tool exposes the model's configuration and the data tables it uses, including their columns, data types, primary keys, and foreign keys. This is the recommended way to discover the exact table and column names needed to build a query. This tool is read-only.

Line 28:		Line 29:
	Every column reports its Name, its ProcessAnalyzer DataType (one of Any, String, Boolean, Integer, Float, DateTime, Duration, ShortString, or Variant), the corresponding DataTypeInDataSource, and a PrimaryKey flag that is true only when the column is a primary key of the data table. Each foreign key defines a TargetDatatable (the referenced data table) and a Columns list of source-to-target column mappings, each mapping a Source column name to a Target column name.		Every column reports its Name, its ProcessAnalyzer DataType (one of Any, String, Boolean, Integer, Float, DateTime, Duration, ShortString, or Variant), the corresponding DataTypeInDataSource, and a PrimaryKey flag that is true only when the column is a primary key of the data table. Each foreign key defines a TargetDatatable (the referenced data table) and a Columns list of source-to-target column mappings, each mapping a Source column name to a Target column name.

	== Generic Query ==		=== Generic Query ===
	Runs a generic analytical query against a QPR ProcessAnalyzer model. Queries are written using the QPR ProcessAnalyzer standard query syntax and expression language, which lets you select a root dataset (such as cases, events, variations, or flows), group it into dimensions, and compute aggregated values. When the processing method is DataFrame (the default and recommended mode), the calculation is executed directly in the data source (Snowflake or SQL Server), and a tabular result with dimension and value columns is returned. The tool supports both case-centric models and object-centric (OCPM/OCEL) models. Despite its analytical power, this tool is read-only: it only reads and aggregates existing data and never modifies it.		Runs a generic analytical query against a QPR ProcessAnalyzer model. Queries are written using the QPR ProcessAnalyzer standard query syntax and expression language, which lets you select a root dataset (such as cases, events, variations, or flows), group it into dimensions, and compute aggregated values. When the processing method is DataFrame (the default and recommended mode), the calculation is executed directly in the data source (Snowflake or SQL Server), and a tabular result with dimension and value columns is returned. The tool supports both case-centric models and object-centric (OCPM/OCEL) models. Despite its analytical power, this tool is read-only: it only reads and aggregates existing data and never modifies it.

Ollvihe at 12:51, 13 August 2026

2026-08-13T12:51:48Z

Show changes

Ollvihe at 12:49, 13 August 2026

2026-08-13T12:49:01Z

Show changes

Ollvihe at 12:39, 13 August 2026

2026-08-13T12:39:45Z

← Older revision		Revision as of 12:39, 13 August 2026
Line 3:		Line 3:
	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]]:		The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]].

	== List Available Process Models ==		== List Available Process Models ==

Ollvihe at 12:39, 13 August 2026

2026-08-13T12:39:37Z

← Older revision		Revision as of 12:39, 13 August 2026
Line 3:		Line 3:
	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language in [[Navigation_Menu#Expression_Designer\|Expression Designer]]:		The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]]:
	~~<pre>~~
	~~Flatten(SystemProjects.Scripts)~~
	~~</pre>~~

	== List Available Process Models ==		== List Available Process Models ==

Ollvihe at 12:36, 13 August 2026

2026-08-13T12:36:30Z

← Older revision		Revision as of 12:36, 13 August 2026
Line 3:		Line 3:
	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language:		The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language in [[Navigation_Menu#Expression_Designer\|Expression Designer]]:
	<pre>		<pre>
	SystemProjects.Scripts~~.Name~~		Flatten(SystemProjects.Scripts)
	</pre>		</pre>

Ollvihe at 10:40, 13 August 2026

2026-08-13T10:40:56Z

← Older revision		Revision as of 10:40, 13 August 2026
Line 2:		Line 2:

	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

			The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language:
			<pre>
			SystemProjects.Scripts.Name
			</pre>

	== List Available Process Models ==		== List Available Process Models ==

Ollvihe at 10:36, 13 August 2026

2026-08-13T10:36:09Z

← Older revision		Revision as of 10:36, 13 August 2026
Line 1:		Line 1:
	QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.		QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.

	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives ~~settings~~]] if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	== List Available Process Models ==		== List Available Process Models ==

Ollvihe at 10:35, 13 August 2026

2026-08-13T10:35:54Z

← Older revision		Revision as of 10:35, 13 August 2026
Line 1:		Line 1:
	QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.		QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.

	It's possible to temporarily disable the built-in MCP ~~tool~~ if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives settings]] if they are undesired.

	== List Available Process Models ==		== List Available Process Models ==