prepare_applications_for_execution
Analyze rule tasks to identify application and credential requirements before execution. Determines whether tasks can share application configurations or require separate credentials for proper setup.
Instructions
Analyze rule tasks and prepare application configuration requirements for execution.
This tool helps users understand what applications are needed and whether they can share applications across multiple tasks.
WHEN TO USE:
Before calling execute_rule() to understand application requirements
To identify if multiple tasks can share the same application
To determine if unique identifiers are needed when using different applications for same appType
NOTE: This tool is optional. Rules with only 'nocredapp' tasks can be executed directly without any application configuration. Use this tool only when tasks require credentials.
APPLICATION SHARING SCENARIOS (when applications are needed):
Shared Application: User wants same credentials for all tasks of an appType
Single application config with basic appTags (just appType)
One application covers multiple tasks
Separate Applications: User needs different credentials per task
Must add unique identifier key (e.g., "purpose") to task appTags
Each application config must include matching unique identifier
No Application Needed: All tasks have 'nocredapp' appType
Skip application configuration entirely
Call execute_rule() with an empty applications list
WORKFLOW:
Call this tool with rule_name
Review which tasks need applications (if any)
If no tasks need applications (all nocredapp): Skip to step 6
For tasks with same appType, decide: share or separate?
If sharing: Provide one application config per appType If separate: Add unique identifiers and provide separate configs
Call execute_rule() with configured applications (or empty list for nocredapp rules)
Args: rule_name: Name of the rule to analyze
Returns: Dict with analysis results and configuration guidance
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rule_name | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||