Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

add_workflow_activity

Add a new activity (e.g., approval, task, notification) to a workflow in ServiceNow by specifying the workflow version ID, activity type, name, and optional attributes.

Instructions

Add a new activity to a workflow in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The main handler function that implements the logic for the 'add_workflow_activity' tool. It processes parameters, makes a POST request to the ServiceNow wf_activity table, and returns the created activity or error.
    def add_workflow_activity(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Add a new activity to a workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for adding a workflow activity
            
        Returns:
            Dict[str, Any]: Added workflow activity details
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, AddWorkflowActivityParams)
        
        # 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)}
        
        # Validate required parameters
        workflow_version_id = params.get("workflow_version_id")
        if not workflow_version_id:
            return {"error": "Workflow version ID is required"}
        
        activity_name = params.get("name")
        if not activity_name:
            return {"error": "Activity name is required"}
        
        # Prepare data for the API request
        data = {
            "workflow_version": workflow_version_id,
            "name": activity_name,
        }
        
        if params.get("description"):
            data["description"] = params["description"]
        
        if params.get("activity_type"):
            data["activity_type"] = params["activity_type"]
        
        if params.get("attributes"):
            # Add any additional attributes
            data.update(params["attributes"])
        
        # Make the API request
        try:
            headers = auth_manager.get_headers()
            url = f"{server_config.instance_url}/api/now/table/wf_activity"
            
            response = requests.post(url, headers=headers, json=data)
            response.raise_for_status()
            
            result = response.json()
            return {
                "activity": result.get("result", {}),
                "message": "Workflow activity added successfully",
            }
        except requests.RequestException as e:
            logger.error(f"Error adding workflow activity: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error adding workflow activity: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining the input schema and validation for the 'add_workflow_activity' tool parameters.
    class AddWorkflowActivityParams(BaseModel):
        """Parameters for adding an activity to a workflow."""
        
        workflow_version_id: str = Field(..., description="Workflow version ID")
        name: str = Field(..., description="Name of the activity")
        description: Optional[str] = Field(None, description="Description of the activity")
        activity_type: str = Field(..., description="Type of activity (e.g., 'approval', 'task', 'notification')")
        attributes: Optional[Dict[str, Any]] = Field(None, description="Additional attributes for the activity")
  • Registration of the 'add_workflow_activity' tool in the central tool definitions dictionary, including the handler function alias, schema, description, and serialization details.
    "add_workflow_activity": (
        add_workflow_activity_tool,
        AddWorkflowActivityParams,
        str,  # Expects JSON string
        "Add a new activity to a workflow in ServiceNow",
        "json_dict",  # Tool returns Pydantic model
  • Import and aliasing of the 'add_workflow_activity' handler function from workflow_tools.py for use in tool registration.
    from servicenow_mcp.tools.workflow_tools import (
        activate_workflow as activate_workflow_tool,
    )
    from servicenow_mcp.tools.workflow_tools import (
        add_workflow_activity as add_workflow_activity_tool,
  • Exposure of the 'add_workflow_activity' tool via __init__.py for convenient imports.
    from servicenow_mcp.tools.workflow_tools import (
        activate_workflow,
        add_workflow_activity,
Behavior2/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 implies a write operation ('Add') but doesn't specify permissions required, whether the addition is reversible, error conditions, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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, no output schema, and 5 nested parameters (via 'params'), the description is incomplete. It lacks details on behavior, parameters, error handling, and relationships to sibling tools, making it insufficient for safe and effective use by an AI agent.

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

Parameters1/5

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

The description mentions no parameters, while the input schema has 1 parameter ('params') with 5 nested properties. With 0% schema description coverage, the description fails to add any semantic context beyond what's in the schema, leaving parameters like 'workflow_version_id' and 'activity_type' unexplained.

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 ('Add a new activity') and resource ('to a workflow in ServiceNow'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'create_workflow' or 'update_workflow_activity', which would require more specificity about what constitutes an 'activity' versus a 'workflow'.

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., needing an existing workflow version), exclusions, or relationships to sibling tools like 'get_workflow_activities' or 'delete_workflow_activity', leaving the agent to infer usage context.

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

Related 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/echelon-ai-labs/servicenow-mcp'

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