Built-in MCP Tools: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| 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 == | ||
Revision as of 10:40, 13 August 2026
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, custom MCP tools can be implemented using scripts.
It's possible to temporarily disable the built-in MCP tools using the 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:
SystemProjects.Scripts.Name