Create MCP Prompts - Revision history

TeeHiet: TK-64701

2026-05-27T12:25:47Z

TK-64701

← Older revision		Revision as of 12:25, 27 May 2026
Line 13:		Line 13:
	The prompt description is a concise metadata field that gives an AI agent instructions on how to achieve complex tasks. When a prompt is called, the associated script is executed and the result is returned as a prompt message.		The prompt description is a concise metadata field that gives an AI agent instructions on how to achieve complex tasks. When a prompt is called, the associated script is executed and the result is returned as a prompt message.

	Every script can define its own prompt configuration as JSON. Supported values are same as [~~http://here~~ https://modelcontextprotocol.io/specification/2025-11-25/server/prompts#prompt], except for the name which is always generated automatically and can't be overridden. Defining the prompt configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the prompt.		Every script can define its own prompt configuration as JSON. Supported values are same as [https://modelcontextprotocol.io/specification/2025-11-25/server/prompts#prompt here], except for the name which is always generated automatically and can't be overridden. Defining the prompt configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the prompt.

	In addition to the name of the prompt, MCP prompts provide the following information to the MCP client:		In addition to the name of the prompt, MCP prompts provide the following information to the MCP client:

TeeHiet: TK-64701

2026-05-27T12:19:13Z

TK-64701

← Older revision		Revision as of 12:19, 27 May 2026
Line 13:		Line 13:
	The prompt description is a concise metadata field that gives an AI agent instructions on how to achieve complex tasks. When a prompt is called, the associated script is executed and the result is returned as a prompt message.		The prompt description is a concise metadata field that gives an AI agent instructions on how to achieve complex tasks. When a prompt is called, the associated script is executed and the result is returned as a prompt message.

	Every script can define its own prompt configuration as JSON. Supported values are same as [http://here https://modelcontextprotocol.io/specification/2025-11-25/server/prompts#prompt], except for the name which is always generated automatically and can't be overridden. Defining the prompt configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the ~~tool~~.		Every script can define its own prompt configuration as JSON. Supported values are same as [http://here https://modelcontextprotocol.io/specification/2025-11-25/server/prompts#prompt], except for the name which is always generated automatically and can't be overridden. Defining the prompt configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the prompt.

	In addition to the name of the prompt, MCP prompts provide the following information to the MCP client:		In addition to the name of the prompt, MCP prompts provide the following information to the MCP client:

TeeHiet: TK-64701

2026-05-27T12:18:08Z

TK-64701

← Older revision		Revision as of 12:18, 27 May 2026
Line 5:		Line 5:
	# Log in to QPR ProcessAnalyzer as a System Administrator.		# Log in to QPR ProcessAnalyzer as a System Administrator.
	# Open or create the script.		# Open or create the script.
	# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP ~~tool~~ name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover prompts with invalid names. The maximum length of the name is 50 characters.		# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP prompt name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover prompts with invalid names. The maximum length of the name is 50 characters.
	# Open the properties of the script.		# Open the properties of the script.
	# Switch to the '''MCP''' tab and select the '''MCP prompt''' option.		# Switch to the '''MCP''' tab and select the '''MCP prompt''' option.

TeeHiet: TK-64701

2026-05-27T12:17:49Z

TK-64701

← Older revision		Revision as of 12:17, 27 May 2026
Line 7:		Line 7:
	# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover prompts with invalid names. The maximum length of the name is 50 characters.		# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover prompts with invalid names. The maximum length of the name is 50 characters.
	# Open the properties of the script.		# Open the properties of the script.
	# Switch to the '''MCP''' tab and select the '''MCP ~~tool~~''' option.		# Switch to the '''MCP''' tab and select the '''MCP prompt''' option.
	# Switch to the '''Description''' tab and provide a description. The description is added to the context of the client.		# Switch to the '''Description''' tab and provide a description. The description is added to the context of the client.

TeeHiet: TK-64701

2026-05-27T12:17:27Z

TK-64701

← Older revision		Revision as of 12:17, 27 May 2026
Line 5:		Line 5:
	# Log in to QPR ProcessAnalyzer as a System Administrator.		# Log in to QPR ProcessAnalyzer as a System Administrator.
	# Open or create the script.		# Open or create the script.
	# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover ~~tools~~ with invalid names. The maximum length of the name is 50 characters.		# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover prompts with invalid names. The maximum length of the name is 50 characters.
	# Open the properties of the script.		# Open the properties of the script.
	# Switch to the '''MCP''' tab and select the '''MCP tool''' option.		# Switch to the '''MCP''' tab and select the '''MCP tool''' option.

TeeHiet: TK-64701

2026-05-27T12:16:52Z

TK-64701

← Older revision		Revision as of 12:16, 27 May 2026
Line 2:		Line 2:
	MCP prompts are implemented using [[Managing_Scripts\|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP prompt when the '''MCP prompt''' option is selected in the [[Managing_Scripts#Script_Properties\|Script Properties]]. Only system administrator users can enable the MCP prompt option. Also, only system administrators can modify scripts that are MCP prompts, because any changes to the MCP interface is restricted to system administrators for security reasons.		MCP prompts are implemented using [[Managing_Scripts\|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP prompt when the '''MCP prompt''' option is selected in the [[Managing_Scripts#Script_Properties\|Script Properties]]. Only system administrator users can enable the MCP prompt option. Also, only system administrators can modify scripts that are MCP prompts, because any changes to the MCP interface is restricted to system administrators for security reasons.

	To enable a script as an MCP ~~Tool~~:		To enable a script as an MCP Prompt:
	# Log in to QPR ProcessAnalyzer as a System Administrator.		# Log in to QPR ProcessAnalyzer as a System Administrator.
	# Open or create the script.		# Open or create the script.
	# For the script to be used as an MCP ~~tool~~, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover tools with invalid names. The maximum length of the name is 50 characters.		# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover tools with invalid names. The maximum length of the name is 50 characters.
	# Open the properties of the script.		# Open the properties of the script.
	# Switch to the '''MCP''' tab and select the '''MCP tool''' option.		# Switch to the '''MCP''' tab and select the '''MCP tool''' option.

TeeHiet: TK-64701

2026-05-27T12:15:34Z

TK-64701

← Older revision		Revision as of 12:15, 27 May 2026
Line 1:		Line 1:
	== Creating MCP Prompts ==		== Creating MCP Prompts ==
	MCP prompts are implemented using [[Managing_Scripts\|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP prompt when the '''MCP prompt''' option is selected in the [[Managing_Scripts#Script_Properties\|Script Properties]]. Only system administrator users can enable the MCP prompt ~~option. Only system administrator users can enable the MCP tool~~ option. Also, only system administrators can modify scripts that are MCP prompts, because any changes to the MCP interface is restricted to system administrators for security reasons.		MCP prompts are implemented using [[Managing_Scripts\|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP prompt when the '''MCP prompt''' option is selected in the [[Managing_Scripts#Script_Properties\|Script Properties]]. Only system administrator users can enable the MCP prompt option. Also, only system administrators can modify scripts that are MCP prompts, because any changes to the MCP interface is restricted to system administrators for security reasons.

	To enable a script as an MCP Tool:		To enable a script as an MCP Tool:

TeeHiet: TK-64701

2026-05-27T12:05:07Z

TK-64701

← Older revision		Revision as of 12:05, 27 May 2026
Line 25:		Line 25:
	* '''meta''': Metadata about the prompt.		* '''meta''': Metadata about the prompt.

	Example prompt configuration:		'''Example''': a full MCP prompt configuration:<syntaxhighlight lang="json">
	<syntaxhighlight lang="json">
	{		{
	"title": "Text Summarizer",		"title": "Text Summarizer",
Line 54:		Line 53:
	}		}
	}		}
	</~~syntaxhilight~~>		</syntaxhighlight>

TeeHiet: TK-64701

2026-05-27T12:01:09Z

TK-64701

New page

== Creating MCP Prompts ==
MCP prompts are implemented using [[Managing_Scripts|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP prompt when the '''MCP prompt''' option is selected in the [[Managing_Scripts#Script_Properties|Script Properties]]. Only system administrator users can enable the MCP prompt option. Only system administrator users can enable the MCP tool option. Also, only system administrators can modify scripts that are MCP prompts, because any changes to the MCP interface is restricted to system administrators for security reasons.

To enable a script as an MCP Tool:
# Log in to QPR ProcessAnalyzer as a System Administrator.
# Open or create the script.
# For the script to be used as an MCP tool, give it a name. This name is then used as the MCP tool name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover tools with invalid names. The maximum length of the name is 50 characters.
# Open the properties of the script.
# Switch to the '''MCP''' tab and select the '''MCP tool''' option.
# Switch to the '''Description''' tab and provide a description. The description is added to the context of the client.

== MCP Prompt Settings ==
The prompt description is a concise metadata field that gives an AI agent instructions on how to achieve complex tasks. When a prompt is called, the associated script is executed and the result is returned as a prompt message.

Every script can define its own prompt configuration as JSON. Supported values are same as [http://here https://modelcontextprotocol.io/specification/2025-11-25/server/prompts#prompt], except for the name which is always generated automatically and can't be overridden. Defining the prompt configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the tool.

In addition to the name of the prompt, MCP prompts provide the following information to the MCP client:
* '''title''': Title of the prompt. Uses the script's title by default.
* '''description''': Description of the prompt. Uses the script's description by default.
* '''arguments''': Following arguments are available to indicate about the MCP prompt:
** '''name'' (required, string): The argument name.
** '''description''' (optional, string): A human-readable description of the argument.
** '''required''' (optional, boolean): Whether the argument must be provided.
* '''icons''': Same as icons for [[Create_MCP_Tools#MCP_Icons|MCP tools]].
* '''meta''': Metadata about the prompt.

Example prompt configuration:
<syntaxhighlight lang="json">
{
"title": "Text Summarizer",
"description": "Generates a concise summary of the provided text",
"arguments": [
{
"name": "text",
"description": "The text content to summarize",
"required": true
},
{
"name": "maxLength",
"description": "Maximum length of the summary in characters",
"required": false
}
],
"icons": [
{
"src": "https://example.com/icons/summarize.svg",
"mimeType": "image/svg+xml",
"sizes": ["any"],
"theme": "light"
}
],
"meta": {
"category": "text-processing"
}
}
</syntaxhilight>