Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

create_group

Create new groups in ServiceNow to organize users and manage permissions. Specify name, description, manager, members, and other group attributes for structured user management.

Instructions

Create a new group in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the group
descriptionNoDescription of the group
managerNoManager of the group (sys_id or username)
parentNoParent group (sys_id or name)
typeNoType of the group
emailNoEmail address for the group
membersNoList of user sys_ids or usernames to add as members
activeNoWhether the group is active

Implementation Reference

  • The core handler function implementing the create_group tool. It constructs a POST request to the ServiceNow sys_user_group table API with the provided parameters, handles optional fields, adds members if specified, and returns a GroupResponse.
    def create_group(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: CreateGroupParams,
    ) -> GroupResponse:
        """
        Create a new group in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for creating the group.
    
        Returns:
            Response with the created group details.
        """
        api_url = f"{config.api_url}/table/sys_user_group"
    
        # Build request data
        data = {
            "name": params.name,
            "active": str(params.active).lower(),
        }
    
        if params.description:
            data["description"] = params.description
        if params.manager:
            data["manager"] = params.manager
        if params.parent:
            data["parent"] = params.parent
        if params.type:
            data["type"] = params.type
        if params.email:
            data["email"] = params.email
    
        # Make request
        try:
            response = requests.post(
                api_url,
                json=data,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", {})
            group_id = result.get("sys_id")
    
            # Add members if provided
            if params.members and group_id:
                add_group_members(
                    config,
                    auth_manager,
                    AddGroupMembersParams(group_id=group_id, members=params.members),
                )
    
            return GroupResponse(
                success=True,
                message="Group created successfully",
                group_id=group_id,
                group_name=result.get("name"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to create group: {e}")
            return GroupResponse(
                success=False,
                message=f"Failed to create group: {str(e)}",
            )
  • Pydantic BaseModel defining the input schema (parameters) for the create_group tool, including required name and optional fields like description, manager, members, etc.
    class CreateGroupParams(BaseModel):
        """Parameters for creating a group."""
    
        name: str = Field(..., description="Name of the group")
        description: Optional[str] = Field(None, description="Description of the group")
        manager: Optional[str] = Field(None, description="Manager of the group (sys_id or username)")
        parent: Optional[str] = Field(None, description="Parent group (sys_id or name)")
        type: Optional[str] = Field(None, description="Type of the group")
        email: Optional[str] = Field(None, description="Email address for the group")
        members: Optional[List[str]] = Field(
            None, description="List of user sys_ids or usernames to add as members"
        )
        active: Optional[bool] = Field(True, description="Whether the group is active")
  • Registration of the 'create_group' tool in the central get_tool_definitions dictionary used by the MCP server. Maps the tool name to its handler (create_group_tool), input schema (CreateGroupParams), return type hint, description, and serialization method.
    "create_group": (
        create_group_tool,
        CreateGroupParams,
        Dict[str, Any],  # Expects dict
        "Create a new group in ServiceNow",
        "raw_dict",
    ),
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 but offers minimal information. It states this is a creation operation, implying it's a write/mutation tool, but doesn't disclose important behavioral aspects like required permissions, whether the group becomes immediately active, what happens on duplicate names, or what the response contains. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 with zero wasted words. It's appropriately sized for a tool with good schema documentation and follows the principle of front-loading the core purpose immediately.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address what the tool returns, what permissions are needed, or how it interacts with sibling tools like 'add_group_members' or 'list_groups'. For a tool that creates persistent resources in a system like ServiceNow, more contextual information would be helpful 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%, with all 8 parameters well-documented in the schema itself. The description adds no parameter information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description, which applies here.

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 ('Create') and resource ('new group in ServiceNow'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'update_group' or 'list_groups' by specifying creation rather than modification or listing. However, it doesn't explicitly differentiate from other creation tools like 'create_user' or 'create_project' beyond the resource type.

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. There's no mention of prerequisites (like required permissions), when to choose this over similar tools, or what happens after creation. With sibling tools like 'add_group_members' and 'update_group' available, the lack of contextual guidance is a significant gap.

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