Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

commit_changeset

Commit a changeset in ServiceNow to finalize and apply configuration or code changes to the platform.

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. It validates parameters, prepares a PATCH request to set the changeset state to 'complete', optionally adds a commit message, and handles the API response.
    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 model defining the input parameters for the commit_changeset tool: 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")
  • Registration of the 'commit_changeset' tool in the central tool_definitions dictionary used by the MCP server, specifying the handler function, params schema, return type, description, and serialization method.
    "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?

No annotations are provided, so the description carries full burden. 'Commit' implies a write/mutation operation, but the description doesn't disclose behavioral traits like whether this is destructive, requires specific permissions, has side effects (e.g., locks changes), or typical outcomes (e.g., success/failure states). It lacks context on what 'commit' means in ServiceNow (e.g., finalizing changes for deployment).

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 waste. It is front-loaded with the core action and resource, making it easy to parse. Every word earns its place without redundancy or fluff.

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?

Given the complexity (a write operation in a platform like ServiceNow), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'commit' entails behaviorally, potential errors, or return values. For a mutation tool with no structured safety or output info, more context is needed to guide the agent effectively.

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 clear descriptions for both parameters ('changeset_id' and 'commit_message'). The description adds no additional meaning beyond the schema, such as format examples or constraints (e.g., changeset_id must be valid). With high schema coverage, the baseline is 3, as 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 'Commit a changeset in ServiceNow' clearly states the action (commit) and resource (changeset) with platform context (ServiceNow). It distinguishes from siblings like 'create_changeset' (creation) and 'publish_changeset' (publishing), but doesn't explicitly differentiate beyond the verb. The purpose is specific and unambiguous.

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. It doesn't mention prerequisites (e.g., requires an existing changeset from 'create_changeset'), when not to use it, or how it relates to siblings like 'publish_changeset' or 'update_changeset'. The agent must infer usage from the name alone.

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