Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

add_comment

Add comments or work notes to ServiceNow incidents to document updates, communicate status, and maintain incident records.

Instructions

Add a comment to an incident in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
incident_idYesIncident ID or sys_id
commentYesComment to add to the incident
is_work_noteNoWhether the comment is a work note

Implementation Reference

  • Implementation of the add_comment tool handler, which adds a comment or work note to a ServiceNow incident by resolving the incident ID if necessary and making a PUT request to the API.
    def add_comment(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: AddCommentParams,
    ) -> IncidentResponse:
        """
        Add a comment to an incident in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for adding the comment.
    
        Returns:
            Response with the result of the operation.
        """
        # 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.is_work_note:
            data["work_notes"] = params.comment
        else:
            data["comments"] = params.comment
    
        # 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="Comment added successfully",
                incident_id=result.get("sys_id"),
                incident_number=result.get("number"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to add comment: {e}")
            return IncidentResponse(
                success=False,
                message=f"Failed to add comment: {str(e)}",
            )
  • Pydantic schema defining the input parameters for the add_comment tool.
    class AddCommentParams(BaseModel):
        """Parameters for adding a comment to an incident."""
    
        incident_id: str = Field(..., description="Incident ID or sys_id")
        comment: str = Field(..., description="Comment to add to the incident")
        is_work_note: bool = Field(False, description="Whether the comment is a work note")
  • Registration of the add_comment tool in the get_tool_definitions dictionary, mapping the tool name to its handler, schema, return type, description, and serialization method.
    "add_comment": (
        add_comment_tool,
        AddCommentParams,
        str,
        "Add a comment to an incident in ServiceNow",
        "str",
    ),
  • Import and re-export of add_comment from incident_tools.py in the tools package __init__.
    from servicenow_mcp.tools.incident_tools import (
        add_comment,
        create_incident,
        list_incidents,
        resolve_incident,
        update_incident,
    )
  • Import of add_comment aliased as add_comment_tool for use in tool registration.
        add_comment as add_comment_tool,
    )
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 the tool adds a comment but doesn't mention permission requirements, whether this is a write operation (implied but not explicit), potential side effects, or what happens on success/failure. 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 and front-loaded with the essential information about what the tool does.

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 and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, or behavioral constraints. The context signals show this is a 3-parameter tool that modifies data, requiring more complete disclosure than provided.

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 three parameters thoroughly. The description doesn't add any additional parameter semantics beyond what's in the schema, meeting the baseline expectation when schema does the heavy lifting.

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 comment') and target resource ('to an incident in ServiceNow'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential sibling comment-related tools (none are listed, but the distinction isn't explicit).

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, prerequisites, or exclusions. It states what the tool does but not when it should be used in context of the sibling tools (like update_incident or resolve_incident).

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