Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

update_incident

Modify and manage existing incidents in ServiceNow by updating fields like assigned user, priority, state, close code, and work notes to streamline incident resolution processes.

Instructions

Update an existing incident in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • Main handler function for the 'update_incident' tool. Determines if incident_id is sys_id or number, queries for sys_id if needed, builds update payload from params, performs PUT request to ServiceNow incident table, returns IncidentResponse.
    def update_incident(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: UpdateIncidentParams,
    ) -> IncidentResponse:
        """
        Update an existing incident in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for updating the incident.
    
        Returns:
            Response with the updated incident details.
        """
        # Determine if incident_id is a number or sys_id
        incident_id = params.incident_id
        if len(incident_id) == 32 and all(c in "0123456789abcdef" for c in incident_id):
            # This is likely a sys_id
            api_url = f"{config.api_url}/table/incident/{incident_id}"
        else:
            # This is likely an incident number
            # First, we need to get the sys_id
            try:
                query_url = f"{config.api_url}/table/incident"
                query_params = {
                    "sysparm_query": f"number={incident_id}",
                    "sysparm_limit": 1,
                }
    
                response = requests.get(
                    query_url,
                    params=query_params,
                    headers=auth_manager.get_headers(),
                    timeout=config.timeout,
                )
                response.raise_for_status()
    
                result = response.json().get("result", [])
                if not result:
                    return IncidentResponse(
                        success=False,
                        message=f"Incident not found: {incident_id}",
                    )
    
                incident_id = result[0].get("sys_id")
                api_url = f"{config.api_url}/table/incident/{incident_id}"
    
            except requests.RequestException as e:
                logger.error(f"Failed to find incident: {e}")
                return IncidentResponse(
                    success=False,
                    message=f"Failed to find incident: {str(e)}",
                )
    
        # Build request data
        data = {}
    
        if params.short_description:
            data["short_description"] = params.short_description
        if params.description:
            data["description"] = params.description
        if params.state:
            data["state"] = params.state
        if params.category:
            data["category"] = params.category
        if params.subcategory:
            data["subcategory"] = params.subcategory
        if params.priority:
            data["priority"] = params.priority
        if params.impact:
            data["impact"] = params.impact
        if params.urgency:
            data["urgency"] = params.urgency
        if params.assigned_to:
            data["assigned_to"] = params.assigned_to
        if params.assignment_group:
            data["assignment_group"] = params.assignment_group
        if params.work_notes:
            data["work_notes"] = params.work_notes
        if params.close_notes:
            data["close_notes"] = params.close_notes
        if params.close_code:
            data["close_code"] = params.close_code
    
        # Make request
        try:
            response = requests.put(
                api_url,
                json=data,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", {})
    
            return IncidentResponse(
                success=True,
                message="Incident updated successfully",
                incident_id=result.get("sys_id"),
                incident_number=result.get("number"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to update incident: {e}")
            return IncidentResponse(
                success=False,
                message=f"Failed to update incident: {str(e)}",
            )
  • Pydantic model defining input parameters for the update_incident tool, including required incident_id and optional fields for updating incident properties.
    class UpdateIncidentParams(BaseModel):
        """Parameters for updating an incident."""
    
        incident_id: str = Field(..., description="Incident ID or sys_id")
        short_description: Optional[str] = Field(None, description="Short description of the incident")
        description: Optional[str] = Field(None, description="Detailed description of the incident")
        state: Optional[str] = Field(None, description="State of the incident")
        category: Optional[str] = Field(None, description="Category of the incident")
        subcategory: Optional[str] = Field(None, description="Subcategory of the incident")
        priority: Optional[str] = Field(None, description="Priority of the incident")
        impact: Optional[str] = Field(None, description="Impact of the incident")
        urgency: Optional[str] = Field(None, description="Urgency of the incident")
        assigned_to: Optional[str] = Field(None, description="User assigned to the incident")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the incident")
        work_notes: Optional[str] = Field(None, description="Work notes to add to the incident")
        close_notes: Optional[str] = Field(None, description="Close notes to add to the incident")
        close_code: Optional[str] = Field(None, description="Close code for the incident")
  • Registration of the 'update_incident' tool in the central tool definitions dictionary, mapping name to (handler function alias, params schema, return type, description, serialization method).
    "update_incident": (
        update_incident_tool,
        UpdateIncidentParams,
        str,
        "Update an existing incident in ServiceNow",
        "str",
    ),
  • Import of the update_incident handler aliased as update_incident_tool for use in tool registration.
        update_incident as update_incident_tool,
    )
  • Re-export of update_incident function in tools package __init__ for convenient imports.
    from servicenow_mcp.tools.incident_tools import (
        add_comment,
        create_incident,
        list_incidents,
        resolve_incident,
        update_incident,
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 states it's an update operation, implying mutation, but doesn't mention required permissions, whether changes are reversible, rate limits, or what the response looks like. 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 no wasted words. It's appropriately sized for a basic tool definition, though it could benefit from more detail given the complexity.

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 14 parameters, 0% schema description coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what fields can be updated, behavioral traits, or return values, leaving significant gaps for 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?

Schema description coverage is 0%, meaning none of the 14 parameters have descriptions in the schema. The tool description adds no information about parameters beyond what's implied by the name 'update_incident', failing to compensate for the complete lack of schema documentation.

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 'Update an existing incident in ServiceNow' clearly states the verb ('update') and resource ('incident'), but it's vague about what specific aspects can be updated and doesn't differentiate from sibling tools like 'resolve_incident' or 'update_change_request'. It's a basic statement of purpose without specificity.

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 'resolve_incident' or 'create_incident', nor any prerequisites or context for usage. The description merely states what it does without indicating appropriate scenarios or exclusions.

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