Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

add_comment

Add comments or work notes to ServiceNow incidents to document updates, track progress, and maintain communication 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

  • The core handler function implementing the add_comment tool logic. It resolves incident ID to sys_id if needed, determines if it's a work note or comment, and sends a PUT request to ServiceNow API to add 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 BaseModel defining the input schema/parameters for the add_comment tool: incident_id (str), comment (str), is_work_note (bool).
    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 used by the MCP server. Maps tool name to handler function alias, params schema, return type hint, 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, it doesn't disclose important behavioral traits: whether this requires specific permissions, if comments are reversible, rate limits, how the comment appears in ServiceNow (public vs private), or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information. However, it could be slightly more structured by explicitly mentioning it's a write operation.

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 incomplete. It doesn't address what the tool returns (success confirmation, comment ID, error details), doesn't mention authentication/permission requirements, and provides no behavioral context. Given the complexity of adding data to a ServiceNow incident, more completeness is needed.

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%, with all parameters well-documented in the schema itself. The description doesn't add any parameter semantics beyond what's already in the schema - it doesn't explain format requirements for incident_id, length limits for comment, or practical implications of is_work_note. Given the high schema coverage, the baseline score of 3 is appropriate.

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 how it differs from other comment-related operations that might exist in ServiceNow.

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 doesn't mention prerequisites (e.g., needing incident access), exclusions (e.g., cannot add comments to resolved incidents), or when to choose other tools like 'update_incident' for comment-related tasks. The sibling tool list includes 'create_incident' and 'resolve_incident' but no explicit comment-related alternatives.

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