Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

update_catalog_category

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

Instructions

Update an existing service catalog category.

Input Schema

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

Implementation Reference

  • The main handler function that performs the PATCH request to update a ServiceNow catalog category using the provided parameters.
    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 model defining the input parameters for the update_catalog_category tool, including category_id (required) and optional fields like title, description, etc.
    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")
  • Registration of the tool in the central tool_definitions dictionary, mapping the tool name to its implementation function, params schema, return type hint, description, and serialization method.
    "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 full burden for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't disclose required permissions, whether changes are reversible, what happens to unspecified fields, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 for a tool with good schema documentation and gets straight to the point without unnecessary elaboration.

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, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'update' entails operationally, what permissions are needed, what the response looks like, or how it differs from similar update tools. The combination of mutation behavior 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 parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 service catalog category'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from other update tools like update_catalog_item or update_category, which would require mentioning it's specifically for catalog categories rather than items or generic categories.

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_catalog_category or list_catalog_categories. It mentions 'existing' which implies a prerequisite (the category must already exist), but offers no explicit when/when-not guidance or comparison to sibling tools.

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