Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

get_changeset_details

Retrieve comprehensive details about a specific ServiceNow changeset using its ID, including change information, status, and implementation details for change management tracking.

Instructions

Get detailed information about a specific changeset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
changeset_idYesChangeset ID or sys_id

Implementation Reference

  • The main handler function implementing the tool logic: validates params, fetches changeset details and associated changes from ServiceNow sys_update_set and sys_update_xml tables via REST API.
    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 tool, with required 'changeset_id' field.
    class GetChangesetDetailsParams(BaseModel):
        """Parameters for getting changeset details."""
    
        changeset_id: str = Field(..., description="Changeset ID or sys_id")
  • Tool registration in the central tool_definitions dictionary, mapping name to handler (aliased import), schema, return type hint, description, and serialization method.
    "get_changeset_details": (
        get_changeset_details_tool,
        GetChangesetDetailsParams,
        str,  # Expects JSON string
        "Get detailed information about a specific changeset",
        "json",  # Tool returns list/dict
    ),
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 'Get detailed information' but doesn't disclose behavioral traits like whether this is a read-only operation, what format the information returns, error conditions, or authentication requirements. For a tool with zero annotation coverage, this is insufficient.

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 zero waste.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, potential return formats, or error handling. For a tool that likely returns complex data (implied by 'details'), more context is needed to guide effective use.

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 the single parameter 'changeset_id' well-documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't clarify what constitutes 'detailed information' or parameter constraints), so the baseline score of 3 is appropriate.

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 verb 'Get' and resource 'detailed information about a specific changeset', making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get_change_request_details' or 'list_changesets', which would require more specific scope definition.

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. With siblings like 'list_changesets' (for listing) and 'get_change_request_details' (for related but different entities), there's no indication of context, prerequisites, or exclusion criteria.

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