Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

add_workflow_activity

Adds a new activity to a ServiceNow workflow version, specifying type, name, and optional details to extend automation processes.

Instructions

Add a new activity to a workflow in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_version_idYesWorkflow version ID
nameYesName of the activity
descriptionNoDescription of the activity
activity_typeYesType of activity (e.g., 'approval', 'task', 'notification')
attributesNoAdditional attributes for the activity

Implementation Reference

  • The main handler function that implements the logic for the 'add_workflow_activity' tool. It validates parameters, prepares the request data, and makes a POST API call to ServiceNow's wf_activity table to create the new activity.
    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/parameters for the 'add_workflow_activity' tool, including required fields like workflow_version_id, name, activity_type, and optional fields.
    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")
  • The registration entry in the central tool_definitions dictionary that maps the tool name 'add_workflow_activity' to its handler function alias, params schema, return type hint, description, and serialization method.
    "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
    ),
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 this is an 'Add' operation (implying creation/mutation) but doesn't address permissions needed, whether the activity becomes active immediately, error conditions, or what the response contains. 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 with zero wasted words. It's appropriately sized for its purpose and front-loads the essential information 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 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after adding (e.g., success response, error handling), doesn't clarify relationships with sibling tools, and provides minimal behavioral context despite the complexity.

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 schema already documents all 5 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate but unenhanced parameter documentation.

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 target resource ('to a workflow in ServiceNow'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'create_workflow' or 'update_workflow_activity', which reduces clarity about its unique scope.

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 like 'create_workflow' or 'update_workflow_activity'. There's no mention of prerequisites (e.g., needing an existing workflow version) or contextual constraints, leaving usage entirely implicit.

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