Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

add_change_task

Add a task to a specific change request in ServiceNow, including details like assigned user, description, and planned start/end dates.

Instructions

Add a task to a change request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The core handler function for the 'add_change_task' tool. It validates input parameters against AddChangeTaskParams, constructs the payload for creating a change task, retrieves instance URL and headers, and performs a POST request to the ServiceNow '/api/now/table/change_task' endpoint.
    def add_change_task(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Add a task to a change request in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for adding a change task.
    
        Returns:
            The created change task.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            AddChangeTaskParams,
            required_fields=["change_id", "short_description"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "change_request": validated_params.change_id,
            "short_description": validated_params.short_description,
        }
        
        # Add optional fields if provided
        if validated_params.description:
            data["description"] = validated_params.description
        if validated_params.assigned_to:
            data["assigned_to"] = validated_params.assigned_to
        if validated_params.planned_start_date:
            data["planned_start_date"] = validated_params.planned_start_date
        if validated_params.planned_end_date:
            data["planned_end_date"] = validated_params.planned_end_date
        
        # Get the instance URL
        instance_url = _get_instance_url(auth_manager, server_config)
        if not instance_url:
            return {
                "success": False,
                "message": "Cannot find instance_url in either server_config or auth_manager",
            }
        
        # Get the headers
        headers = _get_headers(auth_manager, server_config)
        if not headers:
            return {
                "success": False,
                "message": "Cannot find get_headers method in either auth_manager or server_config",
            }
        
        # Add Content-Type header
        headers["Content-Type"] = "application/json"
        
        # Make the API request
        url = f"{instance_url}/api/now/table/change_task"
        
        try:
            response = requests.post(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Change task added successfully",
                "change_task": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error adding change task: {e}")
            return {
                "success": False,
                "message": f"Error adding change task: {str(e)}",
            }
  • Pydantic BaseModel schema defining the input parameters for the add_change_task tool, including required fields like change_id and short_description, and optional fields like description, assigned_to, planned dates.
    class AddChangeTaskParams(BaseModel):
        """Parameters for adding a task to a change request."""
    
        change_id: str = Field(..., description="Change request ID or sys_id")
        short_description: str = Field(..., description="Short description of the task")
        description: Optional[str] = Field(None, description="Detailed description of the task")
        assigned_to: Optional[str] = Field(None, description="User assigned to the task")
        planned_start_date: Optional[str] = Field(None, description="Planned start date (YYYY-MM-DD HH:MM:SS)")
        planned_end_date: Optional[str] = Field(None, description="Planned end date (YYYY-MM-DD HH:MM:SS)")
  • Registers the 'add_change_task' tool in the central tool_definitions dictionary used by the MCP server. Associates the handler function (add_change_task_tool), input schema (AddChangeTaskParams), expected input type (str/JSON), description, and output serialization method ('json_dict').
    "add_change_task": (
        add_change_task_tool,
        AddChangeTaskParams,
        str,  # Expects JSON string
        "Add a task to a change request",
        "json_dict",  # Tool returns Pydantic model
    ),
  • Imports the add_change_task handler from change_tools.py into the tools package namespace, making it available for re-export and use in higher-level registrations.
    from servicenow_mcp.tools.change_tools import (
        add_change_task,
        approve_change,
        create_change_request,
        get_change_request_details,
        list_change_requests,
        reject_change,
        submit_change_for_approval,
        update_change_request,
    )
  • Explicitly includes 'add_change_task' in the __all__ list, ensuring it is exported when the tools package is imported with 'from servicenow_mcp.tools import *'.
    "add_change_task",
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. 'Add a task' implies a write/mutation operation, but the description does not specify permissions required, side effects (e.g., if it triggers notifications or workflows), error conditions, or response format. This leaves critical behavioral traits undocumented for a mutation tool.

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 no wasted words. It is front-loaded and directly states the tool's purpose without unnecessary elaboration, 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?

Given the complexity (a mutation tool with 6 nested parameters), lack of annotations, and no output schema, the description is incomplete. It does not address behavioral aspects, parameter meanings, or usage context, leaving significant gaps for the agent to operate effectively. It only covers the basic purpose, which is insufficient for this tool's needs.

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 6 nested properties (change_id, short_description, etc.). Schema description coverage is 0%, so the schema provides no descriptions for these properties. The description fails to compensate by explaining any parameters, leaving their semantics entirely unclear.

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 'Add a task to a change request' clearly states the action (add) and target resource (task to a change request), making the purpose understandable. It distinguishes from siblings like 'add_comment' or 'add_workflow_activity' by specifying 'task' as the resource type. However, it lacks specificity about what kind of task or context, which prevents a perfect score.

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 does not mention prerequisites (e.g., needing an existing change request), exclusions, or related tools like 'update_change_request' or 'create_change_request' from the sibling list. Without such context, the agent must infer usage from the name alone.

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