Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

get_workflow_activities

Retrieve activities for a ServiceNow workflow to analyze process steps, track task sequences, and understand workflow execution paths.

Instructions

Get activities for a specific workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id
versionNoSpecific version to get activities for

Implementation Reference

  • Main handler function that implements the get_workflow_activities tool. It unwraps params, determines the workflow version (latest published if not specified), queries the wf_activity table via ServiceNow REST API ordered by 'order', and returns activities list with metadata.
    def get_workflow_activities(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Get activities for a specific workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for getting workflow activities
            
        Returns:
            Dict[str, Any]: List of workflow activities
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, GetWorkflowActivitiesParams)
        
        # 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"}
        
        version_id = params.get("version")
        
        # If no version specified, get the latest published version
        if not version_id:
            try:
                headers = auth_manager.get_headers()
                version_url = f"{server_config.instance_url}/api/now/table/wf_workflow_version"
                version_params = {
                    "sysparm_query": f"workflow={workflow_id}^published=true",
                    "sysparm_limit": 1,
                    "sysparm_orderby": "version DESC",
                }
                
                version_response = requests.get(version_url, headers=headers, params=version_params)
                version_response.raise_for_status()
                
                version_result = version_response.json()
                versions = version_result.get("result", [])
                
                if not versions:
                    return {
                        "error": f"No published versions found for workflow {workflow_id}",
                        "workflow_id": workflow_id,
                    }
                
                version_id = versions[0]["sys_id"]
            except requests.RequestException as e:
                logger.error(f"Error getting workflow version: {e}")
                return {"error": str(e)}
            except Exception as e:
                logger.error(f"Unexpected error getting workflow version: {e}")
                return {"error": str(e)}
        
        # Get activities for the version
        try:
            headers = auth_manager.get_headers()
            activities_url = f"{server_config.instance_url}/api/now/table/wf_activity"
            activities_params = {
                "sysparm_query": f"workflow_version={version_id}",
                "sysparm_orderby": "order",
            }
            
            activities_response = requests.get(activities_url, headers=headers, params=activities_params)
            activities_response.raise_for_status()
            
            activities_result = activities_response.json()
            return {
                "activities": activities_result.get("result", []),
                "count": len(activities_result.get("result", [])),
                "workflow_id": workflow_id,
                "version_id": version_id,
            }
        except requests.RequestException as e:
            logger.error(f"Error getting workflow activities: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error getting workflow activities: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining input schema for the tool: requires workflow_id, optional version.
    class GetWorkflowActivitiesParams(BaseModel):
        """Parameters for getting workflow activities."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
        version: Optional[str] = Field(None, description="Specific version to get activities for")
  • MCP tool registration in get_tool_definitions(): maps 'get_workflow_activities' to the handler function, input schema, description, and serialization handling.
    "get_workflow_activities": (
        get_workflow_activities_tool,
        GetWorkflowActivitiesParams,
        str,  # Expects JSON string
        "Get activities for a specific workflow",
        "json",  # Tool returns list/dict
    ),
  • Imports get_workflow_activities from workflow_tools.py into the tools package namespace, making it available for use and export via __all__.
    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 used by get_workflow_activities to normalize input params into a dict from Pydantic model.
    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?

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), but doesn't disclose behavioral traits like whether it returns all activities or filtered ones, pagination, error handling, authentication needs, or rate limits. The description is minimal and lacks necessary context for safe and effective use.

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 and appropriately sized for its purpose, making it easy to scan and understand quickly 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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'activities' are, their format, or any behavioral context. For a tool with two parameters and potential complexity in workflow systems, more detail is needed to guide an AI agent effectively.

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%, so the input schema already documents both parameters ('workflow_id' and 'version') with descriptions. The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or usage examples, meeting the baseline for high schema coverage.

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

Purpose3/5

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

The description 'Get activities for a specific workflow' clearly states the verb ('Get') and resource ('activities'), but it's vague about scope and doesn't distinguish from siblings like 'get_workflow_details' or 'list_workflow_versions'. It specifies 'for a specific workflow' which provides some context, but lacks detail on what 'activities' entail.

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 explicit guidance on when to use this tool versus alternatives such as 'get_workflow_details' or 'list_workflows'. The description implies usage for retrieving activities linked to a workflow, but offers no context on prerequisites, exclusions, or comparison to sibling tools.

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