Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

get_changeset_details

Retrieve detailed information about a specific ServiceNow changeset using its ID, including status, changes, and related data for tracking and analysis.

Instructions

Get detailed information about a specific changeset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
changeset_idYesChangeset ID or sys_id

Implementation Reference

  • The core handler function that retrieves detailed information about a specific changeset by querying the ServiceNow API for both the changeset and its associated changes.
    def get_changeset_details(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Union[Dict[str, Any], GetChangesetDetailsParams],
    ) -> Dict[str, Any]:
        """
        Get detailed information about a specific changeset.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for getting changeset details. Can be a dictionary or a GetChangesetDetailsParams object.
    
        Returns:
            Detailed information about the changeset.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            GetChangesetDetailsParams, 
            required_fields=["changeset_id"]
        )
        
        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",
            }
        
        # Make the API request
        url = f"{instance_url}/api/now/table/sys_update_set/{validated_params.changeset_id}"
        
        try:
            response = requests.get(url, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            # Get the changeset details
            changeset = result.get("result", {})
            
            # Get the changes in this changeset
            changes_url = f"{instance_url}/api/now/table/sys_update_xml"
            changes_params = {
                "sysparm_query": f"update_set={validated_params.changeset_id}",
            }
            
            changes_response = requests.get(changes_url, params=changes_params, headers=headers)
            changes_response.raise_for_status()
            
            changes_result = changes_response.json()
            changes = changes_result.get("result", [])
            
            return {
                "success": True,
                "changeset": changeset,
                "changes": changes,
                "change_count": len(changes),
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error getting changeset details: {e}")
            return {
                "success": False,
                "message": f"Error getting changeset details: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema for the get_changeset_details tool, requiring a changeset_id.
    class GetChangesetDetailsParams(BaseModel):
        """Parameters for getting changeset details."""
    
        changeset_id: str = Field(..., description="Changeset ID or sys_id")
  • Registration of the tool in the central get_tool_definitions dictionary, mapping the tool name to its implementation, params schema, description, and serialization details.
    "get_changeset_details": (
        get_changeset_details_tool,
        GetChangesetDetailsParams,
        str,  # Expects JSON string
        "Get detailed information about a specific changeset",
        "json",  # Tool returns list/dict
    ),
  • Import and alias of the handler function for use in tool registration.
    from servicenow_mcp.tools.changeset_tools import (
        get_changeset_details as get_changeset_details_tool,
    )
  • Export of the tool function via __init__.py to make it available in the tools namespace.
    get_changeset_details,

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
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. It states the tool retrieves information (implying read-only), but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the changeset_id is invalid. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 front-loads the core purpose ('Get detailed information about a specific changeset'). There is zero wasted text, and every word earns its place by clearly conveying the tool's function without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter, read operation) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it fails to explain what 'detailed information' includes or any behavioral context. For a tool that likely returns structured data, more completeness would be helpful despite the simple input.

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 input schema has 100% description coverage, clearly documenting the single required parameter 'changeset_id' as 'Changeset ID or sys_id'. The description adds no additional meaning beyond this, such as format examples or where to find the ID. With high schema coverage, the baseline score of 3 is appropriate 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 clearly states the action ('Get detailed information') and target resource ('about a specific changeset'), which distinguishes it from sibling tools like 'list_changesets' (which lists multiple) and 'update_changeset' (which modifies). However, it doesn't specify what 'detailed information' includes, leaving some ambiguity about the exact scope of data returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when detailed information about a specific changeset is needed, distinguishing it from 'list_changesets' which provides summaries. However, it lacks explicit guidance on when to use alternatives like 'get_change_request_details' or prerequisites (e.g., needing a valid changeset_id). No exclusions or clear when-not-to-use scenarios are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools