Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

deactivate_workflow

Deactivate a workflow in ServiceNow by providing its workflow ID or sys_id to stop automated processes.

Instructions

Deactivate a workflow in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id

Implementation Reference

  • The handler function that executes the deactivation logic by sending a PATCH request to the ServiceNow wf_workflow table to set active=false.
    def deactivate_workflow(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Deactivate a workflow in ServiceNow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for deactivating a workflow
            
        Returns:
            Dict[str, Any]: Deactivated workflow details
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, DeactivateWorkflowParams)
        
        # 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": "false",
        }
        
        # 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 deactivated successfully",
            }
        except requests.RequestException as e:
            logger.error(f"Error deactivating workflow: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error deactivating workflow: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining the input parameters for the tool, requiring workflow_id.
    class DeactivateWorkflowParams(BaseModel):
        """Parameters for deactivating a workflow."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
  • The tool registration entry in get_tool_definitions() that maps 'deactivate_workflow' to its handler, schema, return type, description, and serialization method.
    "deactivate_workflow": (
        deactivate_workflow_tool,
        DeactivateWorkflowParams,
        str,
        "Deactivate a workflow in ServiceNow",
        "str",  # Tool returns simple message
    ),
  • Import of the deactivate_workflow function into the tools package namespace.
    deactivate_workflow,

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is 'deactivate' which implies a state change (likely making the workflow inactive but not deleting it), but doesn't clarify whether this requires special permissions, is reversible, affects dependent processes, or has side effects. The description adds minimal behavioral context beyond the basic action.

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 wasted words. It's appropriately sized for a single-parameter tool and gets straight to the point without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deactivation, whether the operation is reversible, what permissions are required, or what the expected outcome looks like. Given the complexity of workflow management and the lack of structured safety information, more context is needed.

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 single parameter 'workflow_id' well-documented in the schema as 'Workflow ID or sys_id'. The description doesn't add any additional parameter semantics beyond what's already in the structured schema, so it meets the baseline for high schema coverage.

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 ('deactivate') and target resource ('a workflow in ServiceNow'), providing specific verb+resource. However, it doesn't explicitly distinguish this tool from its sibling 'activate_workflow' or other workflow-related tools in the context of when to use deactivation versus deletion or other modifications.

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 'delete_workflow_activity' or 'update_workflow'. The description doesn't mention prerequisites, consequences of deactivation, or when deactivation is appropriate versus other workflow management operations.

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

Deploy Server

Other Tools