Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

add_file_to_changeset

Add a file to a ServiceNow changeset by providing the changeset ID, file path, and file content to manage change-related documentation and attachments.

Instructions

Add a file to a changeset in ServiceNow

Input Schema

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

Implementation Reference

  • The handler function that executes the tool logic: validates parameters, constructs API request to ServiceNow's sys_update_xml table, and adds the file to the specified 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 BaseModel defining the input schema for the tool parameters: changeset_id, file_path, and 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")
  • Registration of the tool in the central tool_definitions dictionary, linking the handler function, input schema, return type hint, 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
    ),
  • Import of the handler function aliased for use in tool registration.
        add_file_to_changeset as add_file_to_changeset_tool,
    )
  • Export/import of the tool handler in the tools package __init__.py for easy access.
    from servicenow_mcp.tools.changeset_tools import (
        add_file_to_changeset,
        commit_changeset,
        create_changeset,
        get_changeset_details,
        list_changesets,
        publish_changeset,
        update_changeset,
    )
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. It doesn't disclose behavioral traits like whether this is a mutation (implied by 'Add'), what permissions are needed, if there are size limits for files, how conflicts are handled, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or side effects. Given the complexity of adding files to changesets (which may involve version control or state changes), more context is needed for the agent to use it 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?

The description adds no parameter semantics beyond what's in the input schema, which has 100% coverage with clear descriptions for all three parameters. The baseline is 3 since the schema does the heavy lifting, but the description doesn't compensate with additional context like file format expectations or path conventions.

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 a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'commit_changeset' or 'publish_changeset' that might also involve changeset operations, so it misses the highest tier.

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., whether a changeset must exist or be in a specific state), nor does it reference sibling tools like 'create_changeset' or 'commit_changeset' for context. This leaves the agent without usage context.

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