Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

create_catalog_category

Create new service catalog categories in ServiceNow to organize and structure catalog items for users. Define title, description, parent category, icon, and order.

Instructions

Create a new service catalog category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle 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

  • Main handler function that implements the create_catalog_category tool by making a POST request to ServiceNow's sc_category table API.
    def create_catalog_category(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: CreateCatalogCategoryParams,
    ) -> CatalogResponse:
        """
        Create a new service catalog category in ServiceNow.
    
        Args:
            config: Server configuration
            auth_manager: Authentication manager
            params: Parameters for creating a catalog category
    
        Returns:
            Response containing the result of the operation
        """
        logger.info("Creating new service catalog category")
        
        # Build the API URL
        url = f"{config.instance_url}/api/now/table/sc_category"
        
        # Prepare request body
        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.post(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"Created catalog category: {params.title}",
                data=formatted_category,
            )
        
        except requests.exceptions.RequestException as e:
            logger.error(f"Error creating catalog category: {str(e)}")
            return CatalogResponse(
                success=False,
                message=f"Error creating catalog category: {str(e)}",
                data=None,
            )
  • Pydantic BaseModel defining the input parameters and validation schema for the create_catalog_category tool.
    class CreateCatalogCategoryParams(BaseModel):
        """Parameters for creating a new service catalog category."""
        
        title: str = Field(..., 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: bool = Field(True, description="Whether the category is active")
        order: Optional[int] = Field(None, description="Order of the category")
  • Tool registration entry in get_tool_definitions() dictionary, associating the tool name with its handler function, schema, description, and serialization method.
    "create_catalog_category": (
        create_catalog_category_tool,
        CreateCatalogCategoryParams,
        str,  # Expects JSON string
        "Create a new service catalog category.",
        "json_dict",  # Tool returns Pydantic model
    ),
  • Import and export of the create_catalog_category function in the tools package __init__.py, making it available for use.
    from servicenow_mcp.tools.catalog_tools import (
        create_catalog_category,
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. It states this is a creation operation but doesn't mention permissions required, whether it's idempotent, what happens on duplicate titles, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 creation tool and gets directly to the point.

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 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'service catalog category' means in this context, what happens after creation, or provide any behavioral context that would help an agent use this tool effectively.

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 has 100% description coverage, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured data, which meets the baseline expectation when schema coverage is complete.

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 service catalog category'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling 'create_category' tool, which appears to serve a similar function but for a different resource type, leaving some ambiguity about when to choose one over the other.

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_category' or 'update_catalog_category'. There's no mention of prerequisites, constraints, or typical use cases, leaving the agent to infer usage from context alone.

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/vparlapalli490/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server