Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

update_catalog_category

Modify an existing service catalog category by updating its title, description, parent category, icon, activation status, or display order in ServiceNow.

Instructions

Update an existing service catalog category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_idYesCategory ID or sys_id
titleNoTitle of the category
descriptionNoDescription of the category
parentNoParent category sys_id
iconNoIcon for the category
activeNoWhether the category is active
orderNoOrder of the category

Implementation Reference

  • The handler function that executes the tool logic: updates a ServiceNow catalog category via PATCH API request.
    def update_catalog_category(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: UpdateCatalogCategoryParams,
    ) -> CatalogResponse:
        """
        Update an existing service catalog category in ServiceNow.
    
        Args:
            config: Server configuration
            auth_manager: Authentication manager
            params: Parameters for updating a catalog category
    
        Returns:
            Response containing the result of the operation
        """
        logger.info(f"Updating service catalog category: {params.category_id}")
        
        # Build the API URL
        url = f"{config.instance_url}/api/now/table/sc_category/{params.category_id}"
        
        # Prepare request body with only the provided parameters
        body = {}
        if params.title is not None:
            body["title"] = params.title
        if params.description is not None:
            body["description"] = params.description
        if params.parent is not None:
            body["parent"] = params.parent
        if params.icon is not None:
            body["icon"] = params.icon
        if params.active is not None:
            body["active"] = str(params.active).lower()
        if params.order is not None:
            body["order"] = str(params.order)
        
        # Make the API request
        headers = auth_manager.get_headers()
        headers["Accept"] = "application/json"
        headers["Content-Type"] = "application/json"
        
        try:
            response = requests.patch(url, headers=headers, json=body)
            response.raise_for_status()
            
            # Process the response
            result = response.json()
            category = result.get("result", {})
            
            # Format the response
            formatted_category = {
                "sys_id": category.get("sys_id", ""),
                "title": category.get("title", ""),
                "description": category.get("description", ""),
                "parent": category.get("parent", ""),
                "icon": category.get("icon", ""),
                "active": category.get("active", ""),
                "order": category.get("order", ""),
            }
            
            return CatalogResponse(
                success=True,
                message=f"Updated catalog category: {params.category_id}",
                data=formatted_category,
            )
        
        except requests.exceptions.RequestException as e:
            logger.error(f"Error updating catalog category: {str(e)}")
            return CatalogResponse(
                success=False,
                message=f"Error updating catalog category: {str(e)}",
                data=None,
            )
  • Pydantic BaseModel defining the input parameters and validation schema for the update_catalog_category tool.
    class UpdateCatalogCategoryParams(BaseModel):
        """Parameters for updating a service catalog category."""
        
        category_id: str = Field(..., description="Category ID or sys_id")
        title: Optional[str] = Field(None, description="Title of the category")
        description: Optional[str] = Field(None, description="Description of the category")
        parent: Optional[str] = Field(None, description="Parent category sys_id")
        icon: Optional[str] = Field(None, description="Icon for the category")
        active: Optional[bool] = Field(None, description="Whether the category is active")
        order: Optional[int] = Field(None, description="Order of the category")
  • Registers the tool in the central get_tool_definitions() dictionary mapping tool name to (handler, schema, return_type, description, serialization).
    "update_catalog_category": (
        update_catalog_category_tool,
        UpdateCatalogCategoryParams,
        str,  # Expects JSON string
        "Update an existing service catalog category.",
        "json_dict",  # Tool returns Pydantic model
    ),
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. It states this is an update operation (implying mutation) but provides no information about permissions required, whether changes are reversible, what happens to unspecified fields, rate limits, or error conditions. The description is minimal and lacks crucial behavioral context for a mutation tool.

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 states the core purpose without any wasted words. It's appropriately sized for a straightforward update operation and is front-loaded with the essential information.

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 7 parameters and no annotations or output schema, the description is inadequate. It doesn't explain what the tool returns, what permissions are needed, whether all fields are optional except category_id, or how partial updates work. The combination of mutation operation, multiple parameters, and lack of structured metadata requires more descriptive context.

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 the schema already documents all 7 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, which is acceptable given the comprehensive schema coverage. The baseline of 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 verb ('Update') and resource ('an existing service catalog category'), making the purpose immediately understandable. It distinguishes from sibling tools like 'create_catalog_category' by specifying 'existing', but doesn't explicitly differentiate from other update tools like 'update_catalog_item' or 'update_category'.

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 doesn't mention prerequisites (e.g., needing a category_id), when not to use it, or how it differs from similar update tools like 'update_category' or 'update_catalog_item' in the sibling list.

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