Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

update_group

Modify an existing ServiceNow group by updating its name, description, manager, parent group, type, email, or active status using the group ID.

Instructions

Update an existing group in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoWhether the group is active
descriptionNoDescription of the group
emailNoEmail address for the group
group_idYesGroup ID or sys_id to update
managerNoManager of the group (sys_id or username)
nameNoName of the group
parentNoParent group (sys_id or name)
typeNoType of the group

Implementation Reference

  • The main handler function for the 'update_group' tool. It performs a PATCH request to the ServiceNow sys_user_group table to update group attributes based on provided parameters.
    def update_group(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: UpdateGroupParams,
    ) -> GroupResponse:
        """
        Update an existing group in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for updating the group.
    
        Returns:
            Response with the updated group details.
        """
        api_url = f"{config.api_url}/table/sys_user_group/{params.group_id}"
    
        # Build request data
        data = {}
        if params.name:
            data["name"] = params.name
        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
        if params.active is not None:
            data["active"] = str(params.active).lower()
    
        # Make request
        try:
            response = requests.patch(
                api_url,
                json=data,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", {})
    
            return GroupResponse(
                success=True,
                message="Group updated successfully",
                group_id=result.get("sys_id"),
                group_name=result.get("name"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to update group: {e}")
            return GroupResponse(
                success=False,
                message=f"Failed to update group: {str(e)}",
            )
  • Pydantic BaseModel defining the input schema/parameters for the update_group tool, including group_id (required) and optional fields like name, description, etc.
    class UpdateGroupParams(BaseModel):
        """Parameters for updating a group."""
    
        group_id: str = Field(..., description="Group ID or sys_id to update")
        name: Optional[str] = Field(None, 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")
        active: Optional[bool] = Field(None, description="Whether the group is active")
  • Tool registration entry in the central tool_definitions dictionary in get_tool_definitions(). Maps 'update_group' to its handler function (aliased), schema, return type, description, and serialization method.
    "update_group": (
        update_group_tool,
        UpdateGroupParams,
        Dict[str, Any],  # Expects dict
        "Update an existing group in ServiceNow",
        "raw_dict",
    ),
  • Export/import of the update_group function in the tools package __init__.py, making it available for import.
    update_group,
  • Pydantic model for the response returned by the update_group handler and other group operations.
    class GroupResponse(BaseModel):
        """Response from group operations."""
    
        success: bool = Field(..., description="Whether the operation was successful")
        message: str = Field(..., description="Message describing the result")
        group_id: Optional[str] = Field(None, description="ID of the affected group")
        group_name: Optional[str] = Field(None, description="Name of the affected group")
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 for behavioral disclosure. While 'Update' implies a mutation, the description doesn't specify whether this requires admin permissions, what happens to unspecified fields (partial vs. full update), whether changes are reversible, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 wasted words. It's appropriately sized and front-loaded with the core purpose.

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 mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects (permissions, side effects), usage context, or return values. The 100% schema coverage helps with parameters but doesn't compensate for other critical gaps.

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%, with all 8 parameters well-documented in the schema itself. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't clarify parameter interactions or provide examples). Baseline 3 is appropriate when the 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 ('Update') and target resource ('an existing group in ServiceNow'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from its sibling 'create_group' or other update tools like 'update_user' or 'update_workflow' 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 like 'create_group' for new groups or 'list_groups' for viewing. It doesn't mention prerequisites (e.g., needing the group_id) or contextual constraints (e.g., permissions required).

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