Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_catalog_category

Create a new service catalog category in ServiceNow to organize and structure catalog items for better service management and user navigation.

Instructions

Create a new service catalog category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoWhether the category is active
descriptionNoDescription of the category
iconNoIcon for the category
orderNoOrder of the category
parentNoParent category sys_id
titleYesTitle of the category

Implementation Reference

  • The handler function implementing the create_catalog_category tool. It constructs a POST request to the ServiceNow sc_category table API with the provided parameters and returns a formatted response.
    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 model defining the input parameters for the create_catalog_category tool, including title, description, parent, icon, active status, and order.
    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")
  • Registration of the create_catalog_category tool in the central tool definitions dictionary, specifying the handler function, params model, return type, 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
    ),
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 a creation operation but doesn't mention whether it requires specific permissions, what happens on success/failure, whether the creation is immediate or queued, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 communicates the core purpose without any wasted words. It's appropriately sized for a straightforward creation tool 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 no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation, what values are returned, error conditions, or how this tool relates to sibling tools. The agent would need to guess about important behavioral aspects of this write operation.

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%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema. According to the 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 verb ('Create') and resource ('new service catalog category'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'create_category' by specifying it's for 'service catalog' categories, though it doesn't explicitly contrast with 'update_catalog_category' or 'list_catalog_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 'update_catalog_category' or 'list_catalog_categories'. It doesn't mention prerequisites, dependencies, or typical use cases, leaving the agent to infer context from the tool name 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/javerthl/servicenow-mcp'

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