Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

list_catalog_items

Retrieve service catalog items from ServiceNow with filtering options for category, search query, and active status.

Instructions

List service catalog items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of catalog items to return
offsetNoOffset for pagination
categoryNoFilter by category
queryNoSearch query for catalog items
activeNoWhether to only return active catalog items

Implementation Reference

  • Main handler function implementing the logic to list ServiceNow service catalog items via REST API, including filtering, pagination, and formatting.
    def list_catalog_items(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListCatalogItemsParams,
    ) -> Dict[str, Any]:
        """
        List service catalog items from ServiceNow.
    
        Args:
            config: Server configuration
            auth_manager: Authentication manager
            params: Parameters for listing catalog items
    
        Returns:
            Dictionary containing catalog items and metadata
        """
        logger.info("Listing service catalog items")
        
        # Build the API URL
        url = f"{config.instance_url}/api/now/table/sc_cat_item"
        
        # Prepare query parameters
        query_params = {
            "sysparm_limit": params.limit,
            "sysparm_offset": params.offset,
            "sysparm_display_value": "true",
            "sysparm_exclude_reference_link": "true",
        }
        
        # Add filters
        filters = []
        if params.active:
            filters.append("active=true")
        if params.category:
            filters.append(f"category={params.category}")
        if params.query:
            filters.append(f"short_descriptionLIKE{params.query}^ORnameLIKE{params.query}")
        
        if filters:
            query_params["sysparm_query"] = "^".join(filters)
        
        # 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()
            items = result.get("result", [])
            
            # Format the response
            formatted_items = []
            for item in items:
                formatted_items.append({
                    "sys_id": item.get("sys_id", ""),
                    "name": item.get("name", ""),
                    "short_description": item.get("short_description", ""),
                    "category": item.get("category", ""),
                    "price": item.get("price", ""),
                    "picture": item.get("picture", ""),
                    "active": item.get("active", ""),
                    "order": item.get("order", ""),
                })
            
            return {
                "success": True,
                "message": f"Retrieved {len(formatted_items)} catalog items",
                "items": formatted_items,
                "total": len(formatted_items),
                "limit": params.limit,
                "offset": params.offset,
            }
        
        except requests.exceptions.RequestException as e:
            logger.error(f"Error listing catalog items: {str(e)}")
            return {
                "success": False,
                "message": f"Error listing catalog items: {str(e)}",
                "items": [],
                "total": 0,
                "limit": params.limit,
                "offset": params.offset,
            }
  • Pydantic BaseModel defining the input schema/parameters for the list_catalog_items tool.
    class ListCatalogItemsParams(BaseModel):
        """Parameters for listing service catalog items."""
        
        limit: int = Field(10, description="Maximum number of catalog items to return")
        offset: int = Field(0, description="Offset for pagination")
        category: Optional[str] = Field(None, description="Filter by category")
        query: Optional[str] = Field(None, description="Search query for catalog items")
        active: bool = Field(True, description="Whether to only return active catalog items")
  • Tool registration entry in get_tool_definitions() mapping 'list_catalog_items' to its handler function, input schema, description, and serialization hint.
    "list_catalog_items": (
        list_catalog_items_tool,
        ListCatalogItemsParams,
        str,  # Expects JSON string
        "List service catalog items.",
        "json",  # Tool returns list/dict
    ),
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 offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, if it requires authentication, how results are structured, or any rate limits. 'List' implies a read operation, but without annotations, more explicit safety/behavior details would help.

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 extremely concise with a single sentence, 'List service catalog items.', which is front-loaded and wastes no words. For a simple list operation, this brevity is appropriate and efficient.

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 tool with 5 parameters. It doesn't explain what the output looks like (e.g., list format, fields returned), which is critical for a list operation. The schema covers inputs well, but the overall context lacks output and behavioral details.

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%, so parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond implying a listing action. This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't compensate with extra context like default behaviors or parameter interactions.

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 'List service catalog items' clearly states the verb ('List') and resource ('service catalog items'), but it's vague about scope and doesn't differentiate from sibling tools like 'list_catalog_categories' or 'get_catalog_item'. It lacks specificity about what exactly gets listed (e.g., all items, filtered items, with what details).

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?

No guidance is provided on when to use this tool versus alternatives like 'get_catalog_item' (for single item) or 'list_catalog_categories' (for categories). The description doesn't mention any prerequisites, context, or exclusions for usage.

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