Skip to main content
Glama
DynamicEndpoints

PowerShell Exec MCP Server

generate_bigfix_relevance_script

Create PowerShell scripts that determine if computers require action in IBM BigFix environments, following best practices for proper output format, logging, and error handling.

Instructions

Generate a BigFix relevance script to determine if computers need action.

Creates a PowerShell relevance script that follows IBM BigFix best practices:
- Proper output format (TRUE/FALSE for BigFix consumption)
- BigFix client log integration for monitoring
- Event log integration for troubleshooting
- Comprehensive error handling and logging
- Fast execution optimized for frequent evaluations

💡 TIP: For complete BigFix deployments, you need BOTH relevance and action scripts.
Consider using 'generate_bigfix_script_pair' to create both scripts together with matching logic.

IBM BigFix References:
- Relevance Language Guide: https://help.hcltechsw.com/bigfix/11.0/relevance/Relevance/c_relevance_language.html
- Action Scripts: https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Console/c_creating_action_scripts.html
- Best Practices: https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Console/c_best_practices_for_creating_fixlets.html
- Client Logging: https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Installation/c_bes_client_logging.html

Args:
    description: Clear description of what the script should check (e.g., 'Check if Chrome needs updating', 'Verify Windows patches are current')
    relevance_logic: PowerShell code that determines relevance. Use 'Complete-Relevance -Relevant $true/$false -Message "status"' to indicate result
    output_path: Optional file path where the script will be saved. If not provided, returns script content
    timeout: Command timeout in seconds (1-300, default 60)
    
Returns:
    Generated script content or path where script was saved
    
Example:
    Generate a script to check if Chrome needs updating:
    ```
    result = await generate_bigfix_relevance_script(
        description="Check if Chrome browser needs updating to version 100.0.0.0 or higher",
        relevance_logic=''',
        try {
            $app = Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" -ErrorAction Stop
            $version = (Get-Item $app.'(Default)').VersionInfo.FileVersion
            $needsUpdate = [version]$version -lt [version]"100.0.0.0"
            Complete-Relevance -Relevant $needsUpdate -Message "Chrome version: $version (Target: 100.0.0.0+)"
        } catch {
            Complete-Relevance -Relevant $true -Message "Chrome not found or inaccessible - installation needed"
        }
        ''',
        output_path="chrome_relevance.ps1"
    )
    ```
    
Tips:
    - Keep relevance logic fast and efficient (evaluated frequently)
    - Return TRUE when action is needed, FALSE when compliant
    - Always use Complete-Relevance function for proper BigFix output format
    - Use try-catch blocks for robust error handling
    - Test relevance logic thoroughly across different environments
    - Use Write-BigFixLog for detailed progress tracking

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYes
relevance_logicYes
output_pathNo
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'generate_bigfix_relevance_script' tool, decorated with @mcp.tool(). It generates BigFix relevance scripts by populating a template with provided description and logic, using the shared generate_script_from_template helper.
    async def generate_bigfix_relevance_script(
        description: str,
        relevance_logic: str,
        output_path: Optional[str] = None,
        timeout: Optional[int] = 60
    ) -> str:
        """Generate a BigFix relevance script to determine if computers need action.
        
        Creates a PowerShell relevance script that follows IBM BigFix best practices:
        - Proper output format (TRUE/FALSE for BigFix consumption)
        - BigFix client log integration for monitoring
        - Event log integration for troubleshooting
        - Comprehensive error handling and logging
        - Fast execution optimized for frequent evaluations
        
        💡 TIP: For complete BigFix deployments, you need BOTH relevance and action scripts.
        Consider using 'generate_bigfix_script_pair' to create both scripts together with matching logic.
        
        IBM BigFix References:
        - Relevance Language Guide: https://help.hcltechsw.com/bigfix/11.0/relevance/Relevance/c_relevance_language.html
        - Action Scripts: https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Console/c_creating_action_scripts.html
        - Best Practices: https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Console/c_best_practices_for_creating_fixlets.html
        - Client Logging: https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Installation/c_bes_client_logging.html
        
        Args:
            description: Clear description of what the script should check (e.g., 'Check if Chrome needs updating', 'Verify Windows patches are current')
            relevance_logic: PowerShell code that determines relevance. Use 'Complete-Relevance -Relevant $true/$false -Message "status"' to indicate result
            output_path: Optional file path where the script will be saved. If not provided, returns script content
            timeout: Command timeout in seconds (1-300, default 60)
            
        Returns:
            Generated script content or path where script was saved
            
        Example:
            Generate a script to check if Chrome needs updating:
            ```
            result = await generate_bigfix_relevance_script(
                description="Check if Chrome browser needs updating to version 100.0.0.0 or higher",
                relevance_logic=''',
                try {
                    $app = Get-ItemProperty "HKLM:\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths\\chrome.exe" -ErrorAction Stop
                    $version = (Get-Item $app.'(Default)').VersionInfo.FileVersion
                    $needsUpdate = [version]$version -lt [version]"100.0.0.0"
                    Complete-Relevance -Relevant $needsUpdate -Message "Chrome version: $version (Target: 100.0.0.0+)"
                } catch {
                    Complete-Relevance -Relevant $true -Message "Chrome not found or inaccessible - installation needed"
                }
                ''',
                output_path="chrome_relevance.ps1"
            )
            ```
            
        Tips:
            - Keep relevance logic fast and efficient (evaluated frequently)
            - Return TRUE when action is needed, FALSE when compliant
            - Always use Complete-Relevance function for proper BigFix output format
            - Use try-catch blocks for robust error handling
            - Test relevance logic thoroughly across different environments
            - Use Write-BigFixLog for detailed progress tracking
        """
        params = {
            "SYNOPSIS": f"BigFix Relevance Script - {description}",
            "DESCRIPTION": description,
            "DATE": datetime.now().strftime('%Y-%m-%d'),
            "RELEVANCE_LOGIC": relevance_logic
        }
        
        if output_path:
            output_path = ensure_directory(output_path)
        
        return await generate_script_from_template("bigfix_relevance", params, output_path, timeout)
  • Helper function used by generate_bigfix_relevance_script (and other tools) to load and populate PowerShell templates from the templates/ directory.
    async def generate_script_from_template(
        template_name: str,
        parameters: Dict[str, Any],
        output_path: Optional[str] = None,
        timeout: Optional[int] = 60
    ) -> str:
        """Generate a PowerShell script from a template.
        
        Args:
            template_name: Name of the template to use (without .ps1 extension)
            parameters: Dictionary of parameters to replace in the template
            output_path: Where to save the generated script (optional)
            timeout: Command timeout in seconds (1-300, default 60)
            
        Returns:
            Generated script content or path where script was saved
        """
        template_path = os.path.join(TEMPLATES_DIR, f"{template_name}.ps1")
        if not os.path.exists(template_path):
            raise ValueError(f"Template {template_name} not found")
            
        with open(template_path, 'r') as f:
            template_content = f.read()
            
        # Replace template variables
        script_content = template_content
        parameters['DATE'] = datetime.now().strftime('%Y-%m-%d')
        
        for key, value in parameters.items():
            script_content = script_content.replace(f"{{{{{key}}}}}", str(value))
            
        if output_path:
            with open(output_path, 'w') as f:
                f.write(script_content)
            return f"Script generated and saved to: {output_path}"
        
        return script_content
  • server.py:587-587 (registration)
    The @mcp.tool() decorator registers the generate_bigfix_relevance_script function as an MCP tool.
    async def generate_bigfix_relevance_script(
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It does an excellent job describing what the tool creates (PowerShell relevance scripts following IBM BigFix best practices), including specific behavioral traits like proper output format, logging integration, error handling, and optimization for frequent evaluations. The only minor gap is it doesn't explicitly mention whether this is a read-only or write operation, though 'generate' implies creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized for a complex tool. It starts with the core purpose, then provides best practices, usage tips, parameter documentation, and a comprehensive example. While lengthy, every section adds value. The only minor deduction is that some information (like the IBM references) could potentially be trimmed without losing core functionality guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, no annotations, 0% schema coverage, but with output schema), the description is remarkably complete. It covers purpose, usage guidelines, behavioral traits, parameter semantics, provides a detailed example, and includes practical tips. The output schema exists, so the description doesn't need to explain return values, and it adequately addresses all other aspects needed for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. Each parameter (description, relevance_logic, output_path, timeout) is clearly explained with examples and usage guidance. The description adds substantial meaning beyond what the bare schema provides, including format requirements, default values, and practical examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Generate a BigFix relevance script to determine if computers need action.' It specifies the verb ('generate'), resource ('BigFix relevance script'), and distinguishes from siblings like 'generate_bigfix_action_script' by focusing on relevance scripts specifically. The tip about needing both relevance and action scripts further clarifies its role in the ecosystem.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool versus alternatives. The tip states: 'For complete BigFix deployments, you need BOTH relevance and action scripts. Consider using 'generate_bigfix_script_pair' to create both scripts together with matching logic.' This clearly indicates when to use this tool (for relevance scripts only) versus when to use the sibling tool (for paired scripts).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DynamicEndpoints/PowerShell-Exec-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server