Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

list_groups

Retrieve ServiceNow groups with filtering options for active status, type, or search terms to manage user permissions and access control.

Instructions

List groups from ServiceNow with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of groups to return
offsetNoOffset for pagination
activeNoFilter by active status
queryNoCase-insensitive search term that matches against group name or description fields. Uses ServiceNow's LIKE operator for partial matching.
typeNoFilter by group type

Implementation Reference

  • The handler function that executes the list_groups tool logic. It queries the ServiceNow sys_user_group table API with pagination, filtering by active, type, and search query, returning a dictionary with success status, message, groups list, and count.
    def list_groups(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListGroupsParams,
    ) -> dict:
        """
        List groups from ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for listing groups.
    
        Returns:
            Dictionary containing list of groups.
        """
        api_url = f"{config.api_url}/table/sys_user_group"
        query_params = {
            "sysparm_limit": str(params.limit),
            "sysparm_offset": str(params.offset),
            "sysparm_display_value": "true",
        }
    
        # Build query
        query_parts = []
        if params.active is not None:
            query_parts.append(f"active={str(params.active).lower()}")
        if params.type:
            query_parts.append(f"type={params.type}")
        if params.query:
            query_parts.append(f"^nameLIKE{params.query}^ORdescriptionLIKE{params.query}")
    
        if query_parts:
            query_params["sysparm_query"] = "^".join(query_parts)
    
        # Make request
        try:
            response = requests.get(
                api_url,
                params=query_params,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", [])
    
            return {
                "success": True,
                "message": f"Found {len(result)} groups",
                "groups": result,
                "count": len(result),
            }
    
        except requests.RequestException as e:
            logger.error(f"Failed to list groups: {e}")
            return {"success": False, "message": f"Failed to list groups: {str(e)}"}
  • Pydantic BaseModel defining the input parameters for the list_groups tool, including limit, offset, active filter, query, and type.
    class ListGroupsParams(BaseModel):
        """Parameters for listing groups."""
    
        limit: int = Field(10, description="Maximum number of groups to return")
        offset: int = Field(0, description="Offset for pagination")
        active: Optional[bool] = Field(None, description="Filter by active status")
        query: Optional[str] = Field(
            None,
            description="Case-insensitive search term that matches against group name or description fields. Uses ServiceNow's LIKE operator for partial matching.",
        )
        type: Optional[str] = Field(None, description="Filter by group type")
  • The tool registration entry in get_tool_definitions() function, associating 'list_groups' name with the handler function, schema, return type hint, description, and serialization method.
    "list_groups": (
        list_groups_tool,
        ListGroupsParams,
        Dict[str, Any],  # Expects dict
        "List groups from ServiceNow with optional filtering",
        "raw_dict",
    ),
  • Re-export of the list_groups function from user_tools.py for convenient access across the tools module.
    list_groups,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a list operation with filtering. It doesn't disclose whether this is a read-only operation (implied but not explicit), whether it requires authentication, rate limits, pagination behavior beyond the schema parameters, or what the output format looks like (no output schema). For a tool with 5 parameters and no annotations, 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 front-loads the core purpose ('List groups from ServiceNow') and adds the key feature ('with optional filtering'). There's zero wasted language, making it appropriately sized for its function.

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 has 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'groups' represent in ServiceNow context, what fields are returned, or behavioral aspects like authentication needs or error handling. For a list operation in a complex system like ServiceNow, this leaves significant gaps for an AI agent.

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%, so the schema already documents all 5 parameters thoroughly. The description adds minimal value by mentioning 'optional filtering' which aligns with parameters like active, query, and type, but doesn't provide additional semantics beyond what's in the schema descriptions. Baseline 3 is appropriate when 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 ('List') and resource ('groups from ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other list_* tools in the sibling set (like list_users, list_incidents), which would require a 5.

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 mentions 'optional filtering' but provides no guidance on when to use this tool versus alternatives. There's no mention of when to use list_groups versus get_user (which might return group memberships) or create_group, nor any prerequisites or context for filtering decisions.

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