Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

add_comment

Add comments or work notes to ServiceNow incidents to document updates, progress, or resolutions for better incident tracking and team collaboration.

Instructions

Add a comment to an incident in ServiceNow

Input Schema

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

Implementation Reference

  • The main handler function for the 'add_comment' tool. It adds a comment or work note to a ServiceNow incident by first resolving the incident ID if necessary, then making a PUT request to update the incident with the comment.
    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 model defining the input parameters for the add_comment tool: incident_id, comment, and is_work_note.
    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 central tool definitions dictionary, mapping the tool name to its implementation (add_comment_tool), params model, return type, description, and serialization method.
    "add_comment": (
        add_comment_tool,
        AddCommentParams,
        str,
        "Add a comment to an incident in ServiceNow",
        "str",
    ),
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. While 'Add a comment' implies a write/mutation operation, the description doesn't disclose important behavioral aspects: required permissions, whether this creates an audit trail, if comments are reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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 front-loaded with the core purpose and appropriately sized for what it communicates. Every word earns its place in this minimal but complete statement of function.

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 happens after comment addition - whether it returns the updated incident, confirmation status, or error details. With 3 parameters and behavioral implications, more context about outcomes, error conditions, and integration with ServiceNow workflows would be needed for completeness.

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 adds no additional parameter semantics beyond what's in the schema - it doesn't explain format requirements for incident_id, comment length limits, or the practical difference between regular comments and work notes. Baseline 3 is appropriate 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 alternatives like 'update_incident' which might also allow comment addition, or explain why this specialized tool exists when there's a general update tool.

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 about when to use this tool versus alternatives. With sibling tools like 'update_incident' available, there's no indication whether this is the preferred method for adding comments or when one might choose this specialized tool over the general update tool. No prerequisites, exclusions, or comparison context is provided.

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/javerthl/servicenow-mcp'

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