Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

update_catalog_item

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

Instructions

Update a service catalog item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
nameNo
short_descriptionNo
descriptionNo
categoryNo
priceNo
activeNo
orderNo

Implementation Reference

  • The core handler function that executes the tool logic by building a PATCH request to update the ServiceNow catalog item (sc_cat_item table) with the provided fields.
    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, including the required item_id and optional fields to update.
    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 update_catalog_item tool in the central tool_definitions dictionary, mapping the name to its implementation function, params model, return type, description, and serialization hint.
    "update_catalog_item": (
        update_catalog_item_tool,
        UpdateCatalogItemParams,
        str,  # Expects JSON string
        "Update a service catalog item.",
        "json",  # 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. 'Update' implies a mutation operation, but the description doesn't mention permission requirements, whether the update is partial or complete, what happens to unspecified fields, error conditions, or response format. For a mutation tool with 8 parameters and no 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 maximally concise - a single sentence with no wasted words. It's front-loaded with the essential action and resource. While it lacks detail, what's present is efficiently structured without redundancy or 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 8 parameters, 0% schema description coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what constitutes a 'service catalog item', what fields are updatable, the update semantics, required permissions, or expected outcomes. The description fails to provide the contextual information needed for an agent to use this tool effectively.

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

Parameters2/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 have descriptions in the schema. The tool description mentions no parameters at all - it doesn't explain what fields can be updated (name, description, price, active status, etc.) or the semantics of the required 'item_id'. With 0% schema coverage and no parameter information in the description, this fails to compensate for the documentation gap.

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 action (update) and resource (service catalog item), which is better than a tautology. However, it doesn't differentiate from sibling tools like 'update_catalog_category' or 'update_catalog_item_variable' - it's a generic update statement without specifying what distinguishes this particular catalog item update operation.

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. With sibling tools like 'update_catalog_category', 'update_catalog_item_variable', and 'get_catalog_item', there's no indication of when this specific update tool is appropriate versus those other catalog-related operations. No prerequisites, exclusions, or alternative recommendations are mentioned.

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