collect_parameter_input
Collects and validates primitive parameter inputs with user confirmation, supporting optional defaults and required fields.
Instructions
Collect user input for non-template parameter inputs.
PARAMETER INPUT PROCESSING:
Collects primitive data type values (STRING, INT, FLOAT, BOOLEAN, DATE, DATETIME)
Stores values in memory (NEVER uploads files for primitive types)
Handles optional vs required inputs based on 'required' attribute
Supports default value confirmation workflow
Validates data types and formats
MANDATORY: Gets final confirmation for EVERY input before proceeding
INPUT REQUIREMENT RULES:
MANDATORY: Only if input.required = true
OPTIONAL: If input.required = false, user can skip or provide value
DEFAULT VALUES: If user requests defaults, must get confirmation
FINAL CONFIRMATION: Always required before proceeding to next input
DEFAULT VALUE WORKFLOW:
User requests to use default values
Show default value to user for confirmation
"I can fill this with the default value: '[default_value]'. Confirm?"
Only proceed after explicit user confirmation
Store confirmed default value in memory
FINAL CONFIRMATION WORKFLOW (MANDATORY):
After user provides value (or confirms default)
Show final confirmation: "You entered: '[value]'. Is this correct? (yes/no)"
If 'yes': Store value and proceed to next input
If 'no': Allow user to re-enter value
NEVER proceed without final confirmation
DATA TYPE VALIDATION:
STRING: Any text value
INT: Integer numbers only
FLOAT: Decimal numbers
BOOLEAN: true/false, yes/no, 1/0
DATE: YYYY-MM-DD format
DATETIME: ISO 8601 format
COLLECTION PRESENTATION: "Now configuring: [X of Y inputs]
Task: {task_name} Input: {input_name} ({data_type}) Description: {description} Required: {Yes/No} Default: {default_value or 'None'}
Please provide a value, type 'default' to use default, or 'skip' if optional:"
CRITICAL RULES:
NEVER upload files for primitive data types
Store all primitive values in memory only
Always confirm default values with user
ALWAYS get final confirmation before proceeding to next input
Respect required vs optional based on input.required attribute
Validate data types before storing
Args: task_name: Name of the task this input belongs to input_name: Name of the input parameter user_value: Value provided by user (optional) use_default: Whether to use default value (requires confirmation)
Returns: Dict containing parameter value and storage info
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_name | Yes | ||
| input_name | Yes | ||
| user_value | No | ||
| use_default | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||