Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

activate_workflow

Activate a ServiceNow workflow to automate business processes by triggering its execution with a specified workflow ID.

Instructions

Activate a workflow in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id

Implementation Reference

  • Core handler function that executes the tool: unwraps params, authenticates, PATCHes the wf_workflow table to set active=true, returns workflow details or error.
    def activate_workflow(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Activate a workflow in ServiceNow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for activating a workflow
            
        Returns:
            Dict[str, Any]: Activated workflow details
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, ActivateWorkflowParams)
        
        # Get the correct auth_manager and server_config
        try:
            auth_manager, server_config = _get_auth_and_config(auth_manager, server_config)
        except ValueError as e:
            logger.error(f"Error getting auth and config: {e}")
            return {"error": str(e)}
        
        workflow_id = params.get("workflow_id")
        if not workflow_id:
            return {"error": "Workflow ID is required"}
        
        # Prepare data for the API request
        data = {
            "active": "true",
        }
        
        # Make the API request
        try:
            headers = auth_manager.get_headers()
            url = f"{server_config.instance_url}/api/now/table/wf_workflow/{workflow_id}"
            
            response = requests.patch(url, headers=headers, json=data)
            response.raise_for_status()
            
            result = response.json()
            return {
                "workflow": result.get("result", {}),
                "message": "Workflow activated successfully",
            }
        except requests.RequestException as e:
            logger.error(f"Error activating workflow: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error activating workflow: {e}")
            return {"error": str(e)}
  • Pydantic model defining input parameters: requires workflow_id (str). Used for validation in the handler.
    class ActivateWorkflowParams(BaseModel):
        """Parameters for activating a workflow."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
  • MCP tool registration in get_tool_definitions(): maps 'activate_workflow' to its handler, schema, description, etc.
    "activate_workflow": (
        activate_workflow_tool,
        ActivateWorkflowParams,
        str,
        "Activate a workflow in ServiceNow",
        "str",  # Tool returns simple message
    ),
  • Imports and exposes activate_workflow from workflow_tools.py for use across the tools module.
    from servicenow_mcp.tools.workflow_tools import (
        activate_workflow,
        add_workflow_activity,
        create_workflow,
        deactivate_workflow,
        delete_workflow_activity,
        get_workflow_activities,
        get_workflow_details,
        list_workflow_versions,
        list_workflows,
        reorder_workflow_activities,
        update_workflow,
        update_workflow_activity,
    )
  • Helper function to normalize input params to dict, used at the start of activate_workflow.
    def _unwrap_params(params: Any, param_class: Type[T]) -> Dict[str, Any]:
        """
        Unwrap parameters if they're wrapped in a Pydantic model.
        This helps handle cases where the parameters are passed as a model instead of a dict.
        """
        if isinstance(params, dict):
            return params
        if isinstance(params, param_class):
            return params.dict(exclude_none=True)
        return params
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this is a read/write operation, permission requirements, side effects (e.g., enabling workflow execution), or error conditions, leaving significant gaps for a mutation tool.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words, making it easy to parse. It's appropriately sized for a simple tool with one parameter and front-loads the essential action and resource.

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

Completeness2/5

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

Given the complexity of a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior, outcomes, error handling, and differentiation from siblings like 'deactivate_workflow', leaving the agent poorly informed for safe and effective use.

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

Parameters3/5

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

Schema description coverage is 100%, with the parameter 'workflow_id' well-documented in the schema as 'Workflow ID or sys_id'. The description adds no additional parameter semantics beyond this, so the baseline score of 3 is appropriate as the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the action ('Activate') and resource ('a workflow in ServiceNow'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'deactivate_workflow' or explain what 'activate' means in this context, preventing a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'deactivate_workflow' or 'update_workflow'. The description lacks context about prerequisites (e.g., workflow must exist, be in a deactivated state) or typical use cases, offering minimal assistance for decision-making.

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/JLKmach/servicenow-mcp'

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