Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

add_file_to_changeset

Add files to ServiceNow changesets to track modifications, manage version control, and document updates during change implementation processes.

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

  • The main handler function implementing the tool logic: validates params, constructs API request to POST file data to sys_update_xml table in ServiceNow.
    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 input schema: changeset_id (str, required), file_path (str, required), file_content (str, required).
    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")
  • Tool registration in get_tool_definitions(): maps 'add_file_to_changeset' to handler function, params model, return type str, description, and serialization 'str'.
    "add_file_to_changeset": (
        add_file_to_changeset_tool,
        AddFileToChangesetParams,
        str,
        "Add a file to 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 for behavioral disclosure. While 'Add' implies a write/mutation operation, the description doesn't specify permissions required, whether the operation is idempotent, error conditions, or what happens if the file already exists in the changeset. 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place.

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 insufficient. It doesn't explain what the tool returns, error handling, side effects, or how it integrates with the broader changeset workflow (e.g., relationship with commit/publish operations). The context signals indicate this tool needs more comprehensive documentation.

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 three parameters clearly documented in the schema. The description doesn't add any additional meaning about parameters beyond what's already in the schema (e.g., format examples, constraints, or relationships between parameters), meeting the baseline for high schema coverage.

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 pairing. However, it doesn't differentiate from sibling tools like 'commit_changeset' or 'publish_changeset' that also operate on changesets, which prevents a perfect score.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing changeset), exclusions, or relationships with sibling tools like 'create_changeset' or 'commit_changeset', leaving usage context unclear.

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