Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

get_catalog_item

Retrieve details of a specific service catalog item from ServiceNow using its ID or sys_id to access service information.

Instructions

Get a specific service catalog item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesCatalog item ID or sys_id

Implementation Reference

  • The handler function that executes the tool logic: fetches catalog item details from ServiceNow sc_cat_item table via REST API, formats response, and includes variables via helper function.
    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 input schema defining the parameters (item_id) for the get_catalog_item tool.
    class GetCatalogItemParams(BaseModel):
        """Parameters for getting a specific service catalog item."""
        
        item_id: str = Field(..., description="Catalog item ID or sys_id")
  • Registration of the 'get_catalog_item' tool in the central tool definitions dictionary used by the MCP server, mapping name to (impl_func, params_model, return_type, description, serialization).
    "get_catalog_item": (
        get_catalog_item_tool,
        GetCatalogItemParams,
        str,  # Expects JSON string
        "Get a specific service catalog item.",
        "json_dict",  # Tool returns Pydantic model
    ),
  • Supporting helper function to retrieve catalog item variables from item_option_new table, called by the handler.
    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 []
  • Pydantic model for the output response structure used by the handler.
    class CatalogResponse(BaseModel):
        """Response from catalog operations."""
    
        success: bool = Field(..., description="Whether the operation was successful")
        message: str = Field(..., description="Message describing the result")
        data: Optional[Dict[str, Any]] = Field(None, description="Response data")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get' which implies a read operation, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the item doesn't exist. For a retrieval tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 simple retrieval tool and front-loads the essential information ('Get a specific service catalog item').

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?

Given no annotations and no output schema, the description is incomplete for a retrieval tool. It doesn't explain what information is returned (item details, metadata, etc.), error handling, or how this differs from similar sibling tools. For a tool in a rich ecosystem with many catalog-related alternatives, more context is needed.

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?

Schema description coverage is 100%, with the single parameter 'item_id' clearly documented as 'Catalog item ID or sys_id'. The description doesn't add any meaning beyond what the schema provides (it doesn't explain ID formats, examples, or constraints), so the baseline score of 3 is appropriate when the schema does the heavy lifting.

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 'Get a specific service catalog item' clearly states the verb 'Get' and resource 'service catalog item', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_catalog_items' or 'get_article', leaving ambiguity about when to use this specific retrieval tool versus other catalog-related tools.

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 'list_catalog_items' (for listing multiple items) and 'get_article' (for retrieving knowledge articles), there's no indication whether this tool is for retrieving individual catalog items by ID versus other retrieval methods or contexts.

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