Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

list_catalog_item_variables

Retrieve variables associated with a ServiceNow catalog item to understand required inputs and configure service requests effectively.

Instructions

List catalog item variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalog_item_idYesThe sys_id of the catalog item
include_detailsNoWhether to include detailed information about each variable
limitNoMaximum number of variables to return
offsetNoOffset for pagination

Implementation Reference

  • The handler function that executes the tool logic. It queries the ServiceNow 'item_option_new' table for variables associated with the specified catalog item ID, supports pagination and detail levels, and returns a structured response.
    def list_catalog_item_variables(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListCatalogItemVariablesParams,
    ) -> ListCatalogItemVariablesResponse:
        """
        List all variables (form fields) for a catalog item.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for listing catalog item variables.
    
        Returns:
            Response with a list of variables for the catalog item.
        """
        # Build query parameters
        query_params = {
            "sysparm_query": f"cat_item={params.catalog_item_id}^ORDERBYorder",
        }
        
        if params.limit:
            query_params["sysparm_limit"] = params.limit
        if params.offset:
            query_params["sysparm_offset"] = params.offset
        
        # Include all fields if detailed info is requested
        if params.include_details:
            query_params["sysparm_display_value"] = "true"
            query_params["sysparm_exclude_reference_link"] = "false"
        else:
            query_params["sysparm_fields"] = "sys_id,name,type,question_text,order,mandatory"
    
        api_url = f"{config.instance_url}/api/now/table/item_option_new"
    
        # Make request
        try:
            response = requests.get(
                api_url,
                params=query_params,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", [])
            
            return ListCatalogItemVariablesResponse(
                success=True,
                message=f"Retrieved {len(result)} variables for catalog item",
                variables=result,
                count=len(result),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to list catalog item variables: {e}")
            return ListCatalogItemVariablesResponse(
                success=False,
                message=f"Failed to list catalog item variables: {str(e)}",
            )
  • Pydantic model defining the input parameters for the list_catalog_item_variables tool, including catalog_item_id (required), include_details, limit, and offset.
    class ListCatalogItemVariablesParams(BaseModel):
        """Parameters for listing catalog item variables."""
    
        catalog_item_id: str = Field(..., description="The sys_id of the catalog item")
        include_details: bool = Field(True, description="Whether to include detailed information about each variable")
        limit: Optional[int] = Field(None, description="Maximum number of variables to return")
        offset: Optional[int] = Field(None, description="Offset for pagination")
  • Pydantic model defining the output response structure for the list_catalog_item_variables tool.
    class ListCatalogItemVariablesResponse(BaseModel):
        """Response from listing catalog item variables."""
    
        success: bool = Field(..., description="Whether the operation was successful")
        message: str = Field(..., description="Message describing the result")
        variables: List[Dict[str, Any]] = Field([], description="List of variables")
        count: int = Field(0, description="Total number of variables found")
  • Import statement in tools/__init__.py that exposes the list_catalog_item_variables function from catalog_variables.py for use in the MCP tools module.
    from servicenow_mcp.tools.catalog_variables import (
        create_catalog_item_variable,
        list_catalog_item_variables,
        update_catalog_item_variable,
    )
  • Inclusion in the __all__ list in tools/__init__.py, registering the tool function for export from the tools module.
    "list_catalog_item_variables",
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 'List' implying a read operation, but doesn't disclose behavioral traits like pagination behavior (implied by limit/offset in schema), rate limits, authentication needs, or what 'variables' entails (e.g., types, format). The description adds minimal value beyond the basic action.

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 waste. It's front-loaded and appropriately sized for its purpose, making it easy to parse without 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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain return values (e.g., structure of variables), error handling, or behavioral nuances like pagination. For a tool with 4 parameters and list functionality, more context is needed to guide effective 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?

Schema description coverage is 100%, providing full parameter documentation. The description adds no additional meaning beyond the schema, such as explaining variable details or usage examples. Baseline is 3 since the schema does the heavy lifting, but no extra context is offered.

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 catalog item variables' clearly states the action (list) and target (catalog item variables), which is adequate. However, it doesn't differentiate from sibling tools like 'get_catalog_item' or 'list_catalog_items', nor does it specify scope (e.g., all variables or filtered). It's functional but lacks specificity for sibling distinction.

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. The description doesn't mention prerequisites (e.g., needing a catalog item ID), exclusions, or related tools like 'create_catalog_item_variable' or 'update_catalog_item_variable'. This leaves the agent without context for appropriate selection.

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