Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

commit_changeset

Commit a changeset in ServiceNow by specifying the changeset ID and optional commit message to finalize updates and ensure version control integration.

Instructions

Commit a changeset in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The core handler function executing the commit_changeset tool: validates params, prepares PATCH request to set changeset state to 'complete', handles auth and returns result.
    def commit_changeset(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Union[Dict[str, Any], CommitChangesetParams],
    ) -> Dict[str, Any]:
        """
        Commit a changeset in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for committing a changeset. Can be a dictionary or a CommitChangesetParams object.
    
        Returns:
            The committed changeset.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            CommitChangesetParams, 
            required_fields=["changeset_id"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "state": "complete",
        }
        
        # Add commit message if provided
        if validated_params.commit_message:
            data["description"] = validated_params.commit_message
        
        # 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/sys_update_set/{validated_params.changeset_id}"
        
        try:
            response = requests.patch(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Changeset committed successfully",
                "changeset": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error committing changeset: {e}")
            return {
                "success": False,
                "message": f"Error committing changeset: {str(e)}",
            }
  • Pydantic BaseModel defining input schema for commit_changeset: requires changeset_id, optional commit_message.
    class CommitChangesetParams(BaseModel):
        """Parameters for committing a changeset."""
    
        changeset_id: str = Field(..., description="Changeset ID or sys_id")
        commit_message: Optional[str] = Field(None, description="Commit message")
  • MCP tool registration in get_tool_definitions dict: maps 'commit_changeset' to aliased handler, schema, return type str, description, and serialization 'str'.
    "commit_changeset": (
        commit_changeset_tool,
        CommitChangesetParams,
        str,
        "Commit a changeset in ServiceNow",
        "str",  # Tool returns simple message
    ),
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this is a destructive/mutative operation, permission requirements, side effects, or what happens post-commit (e.g., status changes). For a tool that likely modifies data, 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 no wasted words. It's front-loaded with the core action and resource, 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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't explain the tool's role in the ServiceNow change management lifecycle, what committing entails, or expected outcomes, leaving the agent with minimal actionable context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what a changeset ID is, where to find it, or the purpose/format of the commit message. With 1 required parameter and 1 optional parameter undocumented, this leaves significant gaps.

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 'Commit a changeset in ServiceNow' clearly states the action (commit) and target resource (changeset) with platform context (ServiceNow). It distinguishes from siblings like 'publish_changeset' by specifying the commit operation rather than publishing, though it doesn't explicitly contrast them.

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 'publish_changeset' or 'update_changeset', nor does it mention prerequisites such as needing an existing changeset. The description lacks context about typical workflow sequencing.

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