Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

list_incidents

Retrieve and filter ServiceNow incident records by state, assignee, category, or search query with pagination controls.

Instructions

List incidents from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of incidents to return
offsetNoOffset for pagination
stateNoFilter by incident state
assigned_toNoFilter by assigned user
categoryNoFilter by category
queryNoSearch query for incidents

Implementation Reference

  • The main handler function that implements the list_incidents tool logic, querying the ServiceNow API for incidents based on parameters and returning formatted results.
    def list_incidents(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListIncidentsParams,
    ) -> dict:
        """
        List incidents from ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for listing incidents.
    
        Returns:
            Dictionary with list of incidents.
        """
        api_url = f"{config.api_url}/table/incident"
    
        # Build query parameters
        query_params = {
            "sysparm_limit": params.limit,
            "sysparm_offset": params.offset,
            "sysparm_display_value": "true",
            "sysparm_exclude_reference_link": "true",
        }
        
        # Add filters
        filters = []
        if params.state:
            filters.append(f"state={params.state}")
        if params.assigned_to:
            filters.append(f"assigned_to={params.assigned_to}")
        if params.category:
            filters.append(f"category={params.category}")
        if params.query:
            filters.append(f"short_descriptionLIKE{params.query}^ORdescriptionLIKE{params.query}")
        
        if filters:
            query_params["sysparm_query"] = "^".join(filters)
        
        # Make request
        try:
            response = requests.get(
                api_url,
                params=query_params,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
            
            data = response.json()
            incidents = []
            
            for incident_data in data.get("result", []):
                # Handle assigned_to field which could be a string or a dictionary
                assigned_to = incident_data.get("assigned_to")
                if isinstance(assigned_to, dict):
                    assigned_to = assigned_to.get("display_value")
                
                incident = {
                    "sys_id": incident_data.get("sys_id"),
                    "number": incident_data.get("number"),
                    "short_description": incident_data.get("short_description"),
                    "description": incident_data.get("description"),
                    "state": incident_data.get("state"),
                    "priority": incident_data.get("priority"),
                    "assigned_to": assigned_to,
                    "category": incident_data.get("category"),
                    "subcategory": incident_data.get("subcategory"),
                    "created_on": incident_data.get("sys_created_on"),
                    "updated_on": incident_data.get("sys_updated_on"),
                }
                incidents.append(incident)
            
            return {
                "success": True,
                "message": f"Found {len(incidents)} incidents",
                "incidents": incidents
            }
            
        except requests.RequestException as e:
            logger.error(f"Failed to list incidents: {e}")
            return {
                "success": False,
                "message": f"Failed to list incidents: {str(e)}",
                "incidents": []
            }
  • Pydantic model defining the input parameters for the list_incidents tool.
    class ListIncidentsParams(BaseModel):
        """Parameters for listing incidents."""
        
        limit: int = Field(10, description="Maximum number of incidents to return")
        offset: int = Field(0, description="Offset for pagination")
        state: Optional[str] = Field(None, description="Filter by incident state")
        assigned_to: Optional[str] = Field(None, description="Filter by assigned user")
        category: Optional[str] = Field(None, description="Filter by category")
        query: Optional[str] = Field(None, description="Search query for incidents")
  • Registration of the list_incidents tool in the central tool definitions dictionary used for MCP server.
    "list_incidents": (
        list_incidents_tool,
        ListIncidentsParams,
        str,  # Expects JSON string
        "List incidents from ServiceNow",
        "json",  # Tool returns list/dict, needs JSON dump
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List incidents from ServiceNow,' which implies a read-only operation, but does not disclose critical traits like whether it requires authentication, has rate limits, returns paginated results, or what the output format is. This leaves significant gaps in understanding the tool's behavior.

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: 'List incidents from ServiceNow.' It is front-loaded and appropriately sized for its purpose, avoiding unnecessary elaboration. Every word earns its place by conveying the core action and resource.

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 complexity (6 parameters, no output schema, no annotations), the description is incomplete. It does not explain the return values, error handling, or behavioral context needed for effective use. While the schema covers parameters well, the lack of output information and behavioral details makes it inadequate for a tool with multiple filtering options.

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, with clear documentation for all 6 parameters (e.g., 'limit' for maximum returns, 'offset' for pagination). The description adds no additional meaning beyond the schema, as it does not explain parameter interactions, default behaviors, or usage examples. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List incidents from ServiceNow' states the verb ('List') and resource ('incidents from ServiceNow'), which clarifies the basic purpose. However, it lacks specificity about scope (e.g., all incidents vs. filtered) and does not distinguish it from sibling tools like 'list_change_requests' or 'list_articles' beyond the resource type. This makes it vague but not tautological.

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. It does not mention any context, prerequisites, or exclusions, such as how it differs from 'create_incident' or 'update_incident' for incident management. Without such information, the agent has no explicit or implied usage cues.

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/vparlapalli490/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server