Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

get_catalog_item

Retrieve detailed information about a specific service catalog item from ServiceNow by providing its unique ID, enabling users to access item specifications and request details.

Instructions

Get a specific service catalog item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesCatalog item ID or sys_id

Implementation Reference

  • The core handler function that implements the 'get_catalog_item' tool. It queries the ServiceNow API for sc_cat_item table by ID, formats the response, fetches variables using a helper, and returns a structured CatalogResponse.
    def get_catalog_item(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: GetCatalogItemParams,
    ) -> CatalogResponse:
        """
        Get a specific service catalog item from ServiceNow.
    
        Args:
            config: Server configuration
            auth_manager: Authentication manager
            params: Parameters for getting a catalog item
    
        Returns:
            Response containing the catalog item details
        """
        logger.info(f"Getting service catalog item: {params.item_id}")
        
        # Build the API URL
        url = f"{config.instance_url}/api/now/table/sc_cat_item/{params.item_id}"
        
        # Prepare query parameters
        query_params = {
            "sysparm_display_value": "true",
            "sysparm_exclude_reference_link": "true",
        }
        
        # Make the API request
        headers = auth_manager.get_headers()
        headers["Accept"] = "application/json"
        
        try:
            response = requests.get(url, headers=headers, params=query_params)
            response.raise_for_status()
            
            # Process the response
            result = response.json()
            item = result.get("result", {})
            
            if not item:
                return CatalogResponse(
                    success=False,
                    message=f"Catalog item not found: {params.item_id}",
                    data=None,
                )
            
            # Format the response
            formatted_item = {
                "sys_id": item.get("sys_id", ""),
                "name": item.get("name", ""),
                "short_description": item.get("short_description", ""),
                "description": item.get("description", ""),
                "category": item.get("category", ""),
                "price": item.get("price", ""),
                "picture": item.get("picture", ""),
                "active": item.get("active", ""),
                "order": item.get("order", ""),
                "delivery_time": item.get("delivery_time", ""),
                "availability": item.get("availability", ""),
                "variables": get_catalog_item_variables(config, auth_manager, params.item_id),
            }
            
            return CatalogResponse(
                success=True,
                message=f"Retrieved catalog item: {item.get('name', '')}",
                data=formatted_item,
            )
        
        except requests.exceptions.RequestException as e:
            logger.error(f"Error getting catalog item: {str(e)}")
            return CatalogResponse(
                success=False,
                message=f"Error getting catalog item: {str(e)}",
                data=None,
            )
  • Pydantic schema defining the input parameters for the get_catalog_item tool: requires item_id (str). Also uses CatalogResponse for output.
    class GetCatalogItemParams(BaseModel):
        """Parameters for getting a specific service catalog item."""
        
        item_id: str = Field(..., description="Catalog item ID or sys_id")
  • Import of the get_catalog_item function in tools/__init__.py, exposing it for MCP tool registration.
    from servicenow_mcp.tools.catalog_tools import (
        create_catalog_category,
        get_catalog_item,
        list_catalog_categories,
        list_catalog_items,
        move_catalog_items,
        update_catalog_category,
    )
  • Supporting helper function called by get_catalog_item to retrieve and format catalog item variables from item_option_new table.
    def get_catalog_item_variables(
        config: ServerConfig,
        auth_manager: AuthManager,
        item_id: str,
    ) -> List[Dict[str, Any]]:
        """
        Get variables for a specific service catalog item.
    
        Args:
            config: Server configuration
            auth_manager: Authentication manager
            item_id: Catalog item ID or sys_id
    
        Returns:
            List of variables for the catalog item
        """
        logger.info(f"Getting variables for catalog item: {item_id}")
        
        # Build the API URL
        url = f"{config.instance_url}/api/now/table/item_option_new"
        
        # Prepare query parameters
        query_params = {
            "sysparm_query": f"cat_item={item_id}^ORDERBYorder",
            "sysparm_display_value": "true",
            "sysparm_exclude_reference_link": "true",
        }
        
        # Make the API request
        headers = auth_manager.get_headers()
        headers["Accept"] = "application/json"
        
        try:
            response = requests.get(url, headers=headers, params=query_params)
            response.raise_for_status()
            
            # Process the response
            result = response.json()
            variables = result.get("result", [])
            
            # Format the response
            formatted_variables = []
            for variable in variables:
                formatted_variables.append({
                    "sys_id": variable.get("sys_id", ""),
                    "name": variable.get("name", ""),
                    "label": variable.get("question_text", ""),
                    "type": variable.get("type", ""),
                    "mandatory": variable.get("mandatory", ""),
                    "default_value": variable.get("default_value", ""),
                    "help_text": variable.get("help_text", ""),
                    "order": variable.get("order", ""),
                })
            
            return formatted_variables
        
        except requests.exceptions.RequestException as e:
            logger.error(f"Error getting catalog item variables: {str(e)}")
            return []
  • The get_catalog_item is listed in __all__, making it available for import and registration in the MCP server.
    "list_catalog_items",
    "get_catalog_item",
    "list_catalog_categories",
    "create_catalog_category",
    "update_catalog_category",
    "move_catalog_items",
    "get_optimization_recommendations",
    "update_catalog_item",
    "create_catalog_item_variable",
    "list_catalog_item_variables",
    "update_catalog_item_variable",
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get[s] a specific service catalog item' but doesn't clarify whether this is a read-only operation, what permissions are required, if it returns structured data or raw content, or any error handling (e.g., for invalid IDs). For a retrieval tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 directly states the tool's purpose without unnecessary words. It is front-loaded with the core action ('Get a specific service catalog item'), making it easy to parse. There is no wasted language or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is relatively simple with one parameter and no output schema. The description covers the basic purpose but lacks details on behavioral aspects like read-only nature, return format, or error conditions. Given the absence of annotations and output schema, it provides a minimal but functional overview, though it could be more informative for reliable agent use.

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 input schema has 100% description coverage, with the 'item_id' parameter clearly documented as 'Catalog item ID or sys_id'. The description doesn't add any additional meaning beyond this, such as format examples or sourcing instructions. Given the high schema coverage, a baseline score of 3 is appropriate as the schema adequately handles parameter documentation.

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 ('Get') and resource ('specific service catalog item'), making the purpose understandable. It distinguishes itself from sibling tools like 'list_catalog_items' by focusing on retrieval of a single item rather than listing multiple items. However, it doesn't specify what 'get' entails (e.g., retrieving details, metadata, or full content), which prevents a perfect score.

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 sibling tools like 'list_catalog_items' for browsing or 'update_catalog_item' for modifications, nor does it specify prerequisites such as needing an item_id. Without this context, the agent must infer usage 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