Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

activate_workflow

Activate ServiceNow workflows to automate processes and trigger automated actions within your instance.

Instructions

Activate a workflow in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id

Implementation Reference

  • The handler function that executes the activate_workflow tool. It unwraps parameters using ActivateWorkflowParams, authenticates, and sends a PATCH request to the ServiceNow wf_workflow table to set the workflow as active.
    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 BaseModel defining the input schema for the activate_workflow tool, which requires a workflow_id.
    class ActivateWorkflowParams(BaseModel):
        """Parameters for activating a workflow."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
  • Central registration of the activate_workflow tool in the tool_definitions dictionary. Maps the tool name to its implementation function, input schema model, return type, description, and serialization hint. This dictionary is loaded by the MCP server to expose the tool.
    "activate_workflow": (
        activate_workflow_tool,
        ActivateWorkflowParams,
        str,
        "Activate a workflow in ServiceNow",
        "str",  # Tool returns simple message
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Activate') but doesn't explain what activation entails (e.g., makes workflow available for use, may require permissions, is irreversible, triggers side effects). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy or fluff.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., side effects, permissions), usage context, or expected outcomes. For a tool that modifies system state, more context is needed to guide 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' clearly documented in the schema as 'Workflow ID or sys_id'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without adding value.

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 immediately understandable. It doesn't explicitly differentiate from sibling tools like 'deactivate_workflow' or 'create_workflow', but the verb 'activate' is specific enough to convey the core function.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., workflow must exist, be in a deactivated state), contrast with 'deactivate_workflow', or explain the context for activation versus creation/update of workflows.

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/vparlapalli490/MCP'

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