Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

list_catalog_item_variables

Retrieve variables associated with a ServiceNow catalog item to configure request forms and automate workflows. Supports pagination and detailed variable information.

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: queries ServiceNow's item_option_new table for variables of a catalog item, supports pagination and details flag.
    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 tool: catalog_item_id (required), include_details, limit, 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 for the tool's response: success, message, variables list, count.
    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")
  • Registration of the tool in the central tool_definitions dictionary used by the MCP server: maps name to (handler, input_schema, return_type, description, serialization).
    "list_catalog_item_variables": (
        list_catalog_item_variables_tool,
        ListCatalogItemVariablesParams,
        Dict[str, Any],  # Expects dict
        "List catalog item variables",
        "dict",  # Tool returns Pydantic model
    ),
  • Import of the handler function into the tools package namespace, exposing it for use in tool_utils.py.
    from servicenow_mcp.tools.catalog_variables import (
        create_catalog_item_variable,
        list_catalog_item_variables,
        update_catalog_item_variable,
    )
Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, whether it requires specific permissions, how results are structured, if there are rate limits, or what happens when no variables exist. The single phrase provides zero behavioral context beyond the basic action implied by 'List'.

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 at just three words with zero wasted text. It's front-loaded with the core action and resource, though this conciseness comes at the cost of completeness. Every word directly contributes to stating the tool's purpose, even if minimally.

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 tool with 4 parameters, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what 'catalog item variables' are, what format the listing returns, or how this tool fits into the broader context of catalog management alongside sibling tools. The minimal description leaves too many contextual gaps for effective 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, providing clear documentation for all 4 parameters. The description adds no parameter information beyond what's already in the schema, so it meets the baseline of 3 for adequate schema coverage without adding value. The description doesn't explain relationships between parameters or provide usage examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List catalog item variables' is a tautology that essentially restates the tool name without adding meaningful context. While it correctly identifies the verb ('List') and resource ('catalog item variables'), it provides no additional specificity about scope, format, or what distinguishes this from similar listing tools like 'list_catalog_items' or 'list_catalog_categories'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or relationships to sibling tools like 'create_catalog_item_variable' or 'update_catalog_item_variable'. An agent would have to infer usage purely from the tool name and parameters.

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