Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

update_catalog_item

Modify service catalog item details including name, description, category, price, and activation status to maintain accurate service offerings.

Instructions

Update a service catalog item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNo
categoryNo
descriptionNo
item_idYes
nameNo
orderNo
priceNo
short_descriptionNo

Implementation Reference

  • The main handler function that performs the PATCH request to update the catalog item in ServiceNow.
    def update_catalog_item(
        config: ServerConfig, auth_manager: AuthManager, params: UpdateCatalogItemParams
    ) -> Dict:
        """
        Update a catalog item.
    
        Args:
            config: The server configuration
            auth_manager: The authentication manager
            params: The parameters for updating the catalog item
    
        Returns:
            A dictionary containing the result of the update operation
        """
        logger.info(f"Updating catalog item: {params.item_id}")
        
        try:
            # Build the request body with only the provided parameters
            body = {}
            if params.name is not None:
                body["name"] = params.name
            if params.short_description is not None:
                body["short_description"] = params.short_description
            if params.description is not None:
                body["description"] = params.description
            if params.category is not None:
                body["category"] = params.category
            if params.price is not None:
                body["price"] = params.price
            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
            url = f"{config.instance_url}/api/now/table/sc_cat_item/{params.item_id}"
            headers = auth_manager.get_headers()
            headers["Content-Type"] = "application/json"
            
            response = requests.patch(url, headers=headers, json=body)
            response.raise_for_status()
            
            return {
                "success": True,
                "message": "Catalog item updated successfully",
                "data": response.json()["result"],
            }
        
        except Exception as e:
            logger.error(f"Error updating catalog item: {e}")
            return {
                "success": False,
                "message": f"Error updating catalog item: {str(e)}",
                "data": None,
            }
  • Pydantic model defining the input parameters for the update_catalog_item tool.
    class UpdateCatalogItemParams(BaseModel):
        """Parameters for updating a catalog item."""
    
        item_id: str
        name: Optional[str] = None
        short_description: Optional[str] = None
        description: Optional[str] = None
        category: Optional[str] = None
        price: Optional[str] = None
        active: Optional[bool] = None
        order: Optional[int] = None
  • Registration of the tool in the central tool definitions dictionary used by the MCP server.
    "update_catalog_item": (
        update_catalog_item_tool,
        UpdateCatalogItemParams,
        str,  # Expects JSON string
        "Update a service catalog item.",
        "json",  # Tool returns Pydantic model
    ),
  • Import of the update_catalog_item function into the tools package namespace.
    from servicenow_mcp.tools.catalog_optimization import (
        get_optimization_recommendations,
        update_catalog_item,
    )
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the action ('update') without disclosing behavioral traits. It doesn't mention permissions required, whether updates are partial or full, what happens to unspecified fields, error conditions, or response format. 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 for a basic tool definition and front-loaded with the core action, though this brevity contributes to gaps in other dimensions.

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, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'update' entails, what fields are modifiable, the update behavior, or expected outcomes, leaving significant gaps for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 8 parameters are documented in the schema. The description adds no parameter information beyond the tool name, failing to compensate for the coverage gap. It doesn't explain what 'item_id', 'active', 'category', etc., represent or how they interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update a service catalog item' clearly states the verb ('update') and resource ('service catalog item'), providing basic purpose. However, it lacks specificity about what aspects can be updated and doesn't differentiate from sibling tools like 'update_catalog_category' or 'update_catalog_item_variable', making it somewhat vague.

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, context for updates, or differentiate from other update tools in the sibling list (e.g., update_catalog_category). This leaves the agent with no usage direction.

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