Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

list_projects

Retrieve and filter ServiceNow projects by state, assignment group, or timeframe to manage project visibility and track progress.

Instructions

List projects from ServiceNow

Input Schema

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

Implementation Reference

  • The main handler function that implements the list_projects tool. It validates input parameters using ListProjectsParams, builds a ServiceNow REST API query based on filters like state, assignment_group, timeframe, and query, then fetches and returns the list of projects.
    def list_projects(
        config: ServerConfig,  # Changed from auth_manager
        auth_manager: AuthManager,  # Changed from server_config
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        List projects from ServiceNow.
    
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for listing projects.
    
        Returns:
            A list of projects.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            ListProjectsParams
        )
        
        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.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, 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, 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/pm_project"
        
        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
            projects = result.get("result", [])
            count = len(projects)
            
            return {
                "success": True,
                "projects": projects,
                "count": count,
                "total": count,  # Use count as total if total is not provided
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error listing projects: {e}")
            return {
                "success": False,
                "message": f"Error listing projects: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema for the list_projects tool, including optional parameters for pagination, filtering by state, group, timeframe, and custom query.
    class ListProjectsParams(BaseModel):
        """Parameters for listing projects."""
    
        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")
        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 in get_tool_definitions dictionary, associating the aliased list_projects_tool function, ListProjectsParams schema, description, and serialization handling.
    "list_projects": (
        list_projects_tool,
        ListProjectsParams,
        str,  # Expects JSON string
        "List projects from ServiceNow",
        "json",  # Tool returns list/dict
    ),
  • Import and alias of the list_projects handler and ListProjectsParams schema from project_tools.py for use in tool registration.
    from servicenow_mcp.tools.project_tools import (
        CreateProjectParams,
        UpdateProjectParams,
        ListProjectsParams,
    )
    from servicenow_mcp.tools.project_tools import (
        create_project as create_project_tool,
        update_project as update_project_tool,
        list_projects as list_projects_tool,
    )
  • Import of list_projects into the tools package __init__.py for exposure to other modules.
    from servicenow_mcp.tools.project_tools import (
        create_project,
        update_project,
        list_projects,
    )
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 doesn't disclose behavioral traits like whether this is a read-only operation (implied by 'list'), pagination behavior (though schema has limit/offset), authentication needs, rate limits, or what the output looks like. 'List projects' suggests a safe read, but no explicit confirmation.

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 extremely concise at 4 words with zero waste. It's front-loaded with the core action and resource. Every word earns its place, though this conciseness comes at the cost of detail.

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 tool with 6 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain return values, error conditions, or behavioral context. While the schema covers parameters well, the overall context for agent usage is incomplete.

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%, so parameters are well-documented in the schema. The description adds no parameter information beyond what's in the schema, but this is acceptable given the high coverage. Baseline 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.

Purpose3/5

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

The description 'List projects from ServiceNow' states the basic action (list) and resource (projects) but is vague about scope and filtering capabilities. It doesn't distinguish this from other list tools like list_articles or list_change_requests, nor does it specify if this lists all projects or has inherent filtering.

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 on when to use this tool versus alternatives. There's no mention of prerequisites, typical use cases, or comparison with sibling tools like get_project (if it existed) or create_project. The agent must infer usage from the name alone.

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