Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

list_story_dependencies

Retrieve story dependencies from ServiceNow to identify relationships between stories, supporting dependency management and project planning.

Instructions

List story dependencies from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dependent_storyNoSys_id of the dependent story is required
limitNoMaximum number of records to return
offsetNoOffset to start from
prerequisite_storyNoSys_id that this story depends on is required
queryNoAdditional query string

Implementation Reference

  • The main handler function that implements the list_story_dependencies tool logic, querying the ServiceNow API for story dependencies based on parameters.
    def list_story_dependencies(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        List story dependencies from ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for listing story dependencies.
    
        Returns:
            A list of story dependencies.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            ListStoryDependenciesParams
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Build the query
        query_parts = []
        
        if validated_params.dependent_story:
            query_parts.append(f"dependent_story={validated_params.dependent_story}")
        if validated_params.prerequisite_story:
            query_parts.append(f"prerequisite_story={validated_params.prerequisite_story}")
        
        # Add any additional query string
        if validated_params.query:
            query_parts.append(validated_params.query)
        
        # Combine query parts
        query = "^".join(query_parts) if query_parts else ""
        
        # Get the instance URL
        instance_url = _get_instance_url(auth_manager, server_config)
        if not instance_url:
            return {
                "success": False,
                "message": "Cannot find instance_url in either server_config or auth_manager",
            }
        
        # Get the headers
        headers = _get_headers(auth_manager, server_config)
        if not headers:
            return {
                "success": False,
                "message": "Cannot find get_headers method in either auth_manager or server_config",
            }
        
        # Make the API request
        url = f"{instance_url}/api/now/table/m2m_story_dependencies"
        
        params = {
            "sysparm_limit": validated_params.limit,
            "sysparm_offset": validated_params.offset,
            "sysparm_query": query,
            "sysparm_display_value": "true",
        }
        
        try:
            response = requests.get(url, headers=headers, params=params)
            response.raise_for_status()
            
            result = response.json()
            
            # Handle the case where result["result"] is a list
            story_dependencies = result.get("result", [])
            count = len(story_dependencies)
            
            return {
                "success": True,
                "story_dependencies": story_dependencies,
                "count": count,
                "total": count,  # Use count as total if total is not provided
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error listing story dependencies: {e}")
            return {
                "success": False,
                "message": f"Error listing story dependencies: {str(e)}",
            }
  • Pydantic model defining the input parameters for the list_story_dependencies tool, including pagination and filtering options.
    class ListStoryDependenciesParams(BaseModel):
        """Parameters for listing story dependencies."""
    
        limit: Optional[int] = Field(10, description="Maximum number of records to return")
        offset: Optional[int] = Field(0, description="Offset to start from")
        query: Optional[str] = Field(None, description="Additional query string")
        dependent_story: Optional[str] = Field(None, description="Sys_id of the dependent story is required")
        prerequisite_story: Optional[str] = Field(None, description="Sys_id that this story depends on is required")
  • Registration of the tool in the central tool definitions dictionary, mapping name to handler, schema, description, etc.
    "list_story_dependencies": (
        list_story_dependencies_tool,
        ListStoryDependenciesParams,
        str,  # Expects JSON string
        "List story dependencies from ServiceNow",
        "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 for behavioral disclosure. 'List' implies a read operation, but the description doesn't specify whether this requires authentication, what permissions are needed, whether results are paginated, or what happens when no dependencies exist. It mentions 'from ServiceNow' but doesn't explain the system context or potential rate limits.

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 at just 5 words. It's front-loaded with the core purpose and wastes no words. Every word earns its place by specifying what's being listed and from where.

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 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'story dependency' actually is in ServiceNow context, what format the results take, or how to interpret the returned data. The agent must rely entirely on parameter names and schema descriptions without understanding the domain semantics.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the structured fields. It doesn't explain how parameters interact (e.g., whether 'dependent_story' and 'prerequisite_story' can be used together) or provide examples of valid query strings.

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 states the tool 'List story dependencies from ServiceNow' which clearly indicates it retrieves dependency information. However, it doesn't specify what format the dependencies are returned in or how they're structured, and it doesn't differentiate from sibling tools like 'create_story_dependency' or 'delete_story_dependency' beyond the basic verb difference.

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. There's no mention of when to use this versus 'list_stories' or how it relates to 'create_story_dependency' and 'delete_story_dependency' operations. The agent must infer usage from the 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