Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

list_change_requests

Retrieve and filter change requests from ServiceNow to monitor IT infrastructure modifications, track progress, and manage approvals.

Instructions

List change requests from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return
offsetNoOffset to start from
stateNoFilter by state
typeNoFilter by type (normal, standard, emergency)
categoryNoFilter by category
assignment_groupNoFilter by assignment group
timeframeNoFilter by timeframe (upcoming, in-progress, completed)
queryNoAdditional query string

Implementation Reference

  • Main handler function that executes the list_change_requests tool: validates input params using ListChangeRequestsParams, constructs ServiceNow Table API query based on filters, fetches change requests via GET request, and returns formatted result.
    def list_change_requests(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        List change requests from ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for listing change requests.
    
        Returns:
            A list of change requests.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            ListChangeRequestsParams
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Build the query
        query_parts = []
        
        if validated_params.state:
            query_parts.append(f"state={validated_params.state}")
        if validated_params.type:
            query_parts.append(f"type={validated_params.type}")
        if validated_params.category:
            query_parts.append(f"category={validated_params.category}")
        if validated_params.assignment_group:
            query_parts.append(f"assignment_group={validated_params.assignment_group}")
        
        # Handle timeframe filtering
        if validated_params.timeframe:
            now = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
            if validated_params.timeframe == "upcoming":
                query_parts.append(f"start_date>{now}")
            elif validated_params.timeframe == "in-progress":
                query_parts.append(f"start_date<{now}^end_date>{now}")
            elif validated_params.timeframe == "completed":
                query_parts.append(f"end_date<{now}")
        
        # Add any additional query string
        if validated_params.query:
            query_parts.append(validated_params.query)
        
        # Combine query parts
        query = "^".join(query_parts) if query_parts else ""
        
        # 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/change_request"
        
        params = {
            "sysparm_limit": validated_params.limit,
            "sysparm_offset": validated_params.offset,
            "sysparm_query": query,
            "sysparm_display_value": "true",
        }
        
        try:
            response = requests.get(url, headers=headers, params=params)
            response.raise_for_status()
            
            result = response.json()
            
            # Handle the case where result["result"] is a list
            change_requests = result.get("result", [])
            count = len(change_requests)
            
            return {
                "success": True,
                "change_requests": change_requests,
                "count": count,
                "total": count,  # Use count as total if total is not provided
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error listing change requests: {e}")
            return {
                "success": False,
                "message": f"Error listing change requests: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema/parameters for the list_change_requests tool, including pagination (limit/offset), filters (state, type, etc.), and custom query.
    class ListChangeRequestsParams(BaseModel):
        """Parameters for listing change requests."""
    
        limit: Optional[int] = Field(10, description="Maximum number of records to return")
        offset: Optional[int] = Field(0, description="Offset to start from")
        state: Optional[str] = Field(None, description="Filter by state")
        type: Optional[str] = Field(None, description="Filter by type (normal, standard, emergency)")
        category: Optional[str] = Field(None, description="Filter by category")
        assignment_group: Optional[str] = Field(None, description="Filter by assignment group")
        timeframe: Optional[str] = Field(None, description="Filter by timeframe (upcoming, in-progress, completed)")
        query: Optional[str] = Field(None, description="Additional query string")
  • Tool registration/definition in get_tool_definitions() dict: maps 'list_change_requests' to its handler (aliased), schema (ListChangeRequestsParams), description, and serialization handling for MCP server.
    "list_change_requests": (
        list_change_requests_tool,
        ListChangeRequestsParams,
        str,  # Expects JSON string
        "List change requests from ServiceNow",
        "json",  # Tool returns list/dict
    ),
  • Import and export of list_change_requests function from change_tools.py into tools package __init__, making it available for registration.
    from servicenow_mcp.tools.change_tools import (
        add_change_task,
        approve_change,
        create_change_request,
        get_change_request_details,
        list_change_requests,
        reject_change,
        submit_change_for_approval,
        update_change_request,
    )
  • Shared helper function used by list_change_requests (and other tools) to unwrap, validate input params against Pydantic model, and handle common formatting issues.
    def _unwrap_and_validate_params(params: Any, model_class: Type[T], required_fields: List[str] = None) -> Dict[str, Any]:
        """
        Helper function to unwrap and validate parameters.
        
        Args:
            params: The parameters to unwrap and validate.
            model_class: The Pydantic model class to validate against.
            required_fields: List of required field names.
            
        Returns:
            A tuple of (success, result) where result is either the validated parameters or an error message.
        """
        # Handle case where params might be wrapped in another dictionary
        if isinstance(params, dict) and len(params) == 1 and "params" in params and isinstance(params["params"], dict):
            logger.warning("Detected params wrapped in a 'params' key. Unwrapping...")
            params = params["params"]
        
        # Handle case where params might be a Pydantic model object
        if not isinstance(params, dict):
            try:
                # Try to convert to dict if it's a Pydantic model
                logger.warning("Params is not a dictionary. Attempting to convert...")
                params = params.dict() if hasattr(params, "dict") else dict(params)
            except Exception as e:
                logger.error(f"Failed to convert params to dictionary: {e}")
                return {
                    "success": False,
                    "message": f"Invalid parameters format. Expected a dictionary, got {type(params).__name__}",
                }
        
        # Validate required parameters are present
        if required_fields:
            for field in required_fields:
                if field not in params:
                    return {
                        "success": False,
                        "message": f"Missing required parameter '{field}'",
                    }
        
        try:
            # Validate parameters against the model
            validated_params = model_class(**params)
            return {
                "success": True,
                "params": validated_params,
            }
        except Exception as e:
            logger.error(f"Error validating parameters: {e}")
            return {
                "success": False,
                "message": f"Error validating parameters: {str(e)}",
            }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List change requests' implies a read-only operation, but the description doesn't mention pagination behavior (despite limit/offset parameters), sorting defaults, authentication requirements, rate limits, or what fields are returned. For a tool with 8 parameters and no annotation coverage, this is insufficient behavioral context.

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 gets straight to the point. There's zero waste or redundancy. It's appropriately sized for a list operation and front-loaded with the essential information.

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 (8 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain what a 'change request' is in ServiceNow context, what fields are returned, how results are ordered, or any behavioral constraints. For a list operation with filtering capabilities, more context is needed to help an agent 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 schema description coverage is 100%, with each parameter well-documented in the schema itself. The description adds no parameter information beyond what's already in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'List change requests from ServiceNow' clearly states the verb ('List') and resource ('change requests'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other list tools in the sibling set (like list_incidents, list_stories, etc.), which would require specifying what makes change requests distinct.

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 many sibling tools available (like get_change_request_details for single records or create_change_request for creation), there's no indication of when this list operation is appropriate versus other change request operations or other list operations.

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