Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

commit_changeset

Commit a changeset in ServiceNow to finalize and apply pending configuration or data changes using the specified changeset ID and optional commit message.

Instructions

Commit a changeset in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
changeset_idYesChangeset ID or sys_id
commit_messageNoCommit message

Implementation Reference

  • The main handler function that implements the commit_changeset tool logic. It validates parameters, prepares a PATCH request to set the changeset state to 'complete', optionally updates the description with commit message, and returns success or error.
    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 the input schema for the commit_changeset tool, with required 'changeset_id' and 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")
  • Tool registration in the get_tool_definitions() dictionary: maps 'commit_changeset' to its handler (commit_changeset_tool), input schema (CommitChangesetParams), return type (str), description, and serialization method ('str').
    "commit_changeset": (
        commit_changeset_tool,
        CommitChangesetParams,
        str,
        "Commit a changeset in ServiceNow",
        "str",  # Tool returns simple message
    ),
  • Helper function used by commit_changeset (and other tools) to unwrap input parameters (dict or Pydantic model), validate against the schema, check required fields, and return validated params or error.
    def _unwrap_and_validate_params(
        params: Union[Dict[str, Any], BaseModel], 
        model_class: Type[T], 
        required_fields: Optional[List[str]] = None
    ) -> Dict[str, Any]:
        """
        Unwrap and validate parameters.
    
        Args:
            params: The parameters to unwrap and validate. Can be a dictionary or a Pydantic model.
            model_class: The Pydantic model class to validate against.
            required_fields: List of fields that must be present.
    
        Returns:
            A dictionary with success status and validated parameters or error message.
        """
        try:
            # Handle case where params is already a Pydantic model
            if isinstance(params, BaseModel):
                # If it's already the correct model class, use it directly
                if isinstance(params, model_class):
                    model_instance = params
                # Otherwise, convert to dict and create new instance
                else:
                    model_instance = model_class(**params.dict())
            # Handle dictionary case
            else:
                # Create model instance
                model_instance = model_class(**params)
            
            # Check required fields
            if required_fields:
                missing_fields = []
                for field in required_fields:
                    if getattr(model_instance, field, None) is None:
                        missing_fields.append(field)
                
                if missing_fields:
                    return {
                        "success": False,
                        "message": f"Missing required fields: {', '.join(missing_fields)}",
                    }
            
            return {
                "success": True,
                "params": model_instance,
            }
        except Exception as e:
            return {
                "success": False,
                "message": f"Invalid parameters: {str(e)}",
            }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'commit' implies a write/mutation operation, the description doesn't clarify what committing entails (e.g., finalizing changes, triggering workflows, requiring permissions), whether it's reversible, or what side effects might occur. This leaves significant gaps for a mutation tool.

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 extremely concise with a single, direct sentence that states the tool's purpose without any wasted words. It's appropriately sized for a straightforward operation and front-loaded with the essential information.

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 inadequate. It doesn't explain what 'commit' means operationally, what happens after committing, potential side effects, or how this differs from related sibling tools. The context signals indicate this is a non-trivial operation in a complex ServiceNow environment, requiring more 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%, with both parameters ('changeset_id' and 'commit_message') clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline of 3 where the 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 ('commit') and target resource ('a changeset in ServiceNow'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'publish_changeset' or 'update_changeset', which might have related functionality in the ServiceNow context.

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. With sibling tools like 'publish_changeset', 'update_changeset', and 'create_changeset' available, there's no indication of the specific context or workflow stage where 'commit_changeset' should be invoked, nor any prerequisites or exclusions mentioned.

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