Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

add_file_to_changeset

Add files to ServiceNow changesets by specifying file paths and content. This tool enables developers to manage code changes and documentation within ServiceNow development workflows.

Instructions

Add a file to a changeset in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
changeset_idYesChangeset ID or sys_id
file_pathYesPath of the file to add
file_contentYesContent of the file

Implementation Reference

  • Implements the core logic for adding a file to a ServiceNow changeset by posting to the sys_update_xml table with the file path, content, and linking to the changeset.
    def add_file_to_changeset(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Union[Dict[str, Any], AddFileToChangesetParams],
    ) -> Dict[str, Any]:
        """
        Add a file to a changeset in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for adding a file to a changeset. Can be a dictionary or a AddFileToChangesetParams object.
    
        Returns:
            The result of the add file operation.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            AddFileToChangesetParams, 
            required_fields=["changeset_id", "file_path", "file_content"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # 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"
        
        # Prepare the request data for adding a file
        data = {
            "update_set": validated_params.changeset_id,
            "name": validated_params.file_path,
            "payload": validated_params.file_content,
            "type": "file",
        }
        
        # Make the API request
        url = f"{instance_url}/api/now/table/sys_update_xml"
        
        try:
            response = requests.post(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "File added to changeset successfully",
                "file": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error adding file to changeset: {e}")
            return {
                "success": False,
                "message": f"Error adding file to changeset: {str(e)}",
            } 
  • Pydantic model defining the input parameters for the add_file_to_changeset tool: changeset_id, file_path, file_content.
    class AddFileToChangesetParams(BaseModel):
        """Parameters for adding a file to a changeset."""
    
        changeset_id: str = Field(..., description="Changeset ID or sys_id")
        file_path: str = Field(..., description="Path of the file to add")
        file_content: str = Field(..., description="Content of the file")
  • Registers the 'add_file_to_changeset' tool in the get_tool_definitions dictionary, mapping the imported function, params schema, return type, description, and serialization method.
    "add_file_to_changeset": (
        add_file_to_changeset_tool,
        AddFileToChangesetParams,
        str,
        "Add a file to a changeset in ServiceNow",
        "str",  # Tool returns simple message
    ),
  • Re-exports the add_file_to_changeset function from changeset_tools for use in the tools package.
    from servicenow_mcp.tools.changeset_tools import (
        add_file_to_changeset,
        commit_changeset,
        create_changeset,
        get_changeset_details,
        list_changesets,
        publish_changeset,
        update_changeset,
    )
  • Imports the add_file_to_changeset function (aliased as _tool) and AddFileToChangesetParams from changeset_tools for registration in tool definitions.
    from servicenow_mcp.tools.changeset_tools import (
        add_file_to_changeset as add_file_to_changeset_tool,
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 basic action without disclosing behavioral traits. It doesn't mention whether this is a mutation (likely), what permissions are required, if files can be overwritten, error conditions, or response format. This leaves significant gaps for a tool that modifies data.

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 that states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste or redundancy.

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 tool's complexity (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what happens after adding a file, error handling, or integration with sibling tools like 'commit_changeset', leaving the agent with incomplete operational context.

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%, providing clear documentation for all three parameters. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline of 3 where the schema does the heavy lifting without compensating value.

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 file') and target resource ('to a changeset in ServiceNow'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'create_changeset' or 'commit_changeset', which would require explicit comparison to achieve a score of 5.

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. There's no mention of prerequisites (e.g., needing an existing changeset), exclusions, or comparisons to sibling tools like 'create_changeset' or 'update_changeset', leaving the agent without contextual usage instructions.

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