Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

list_scrum_tasks

Retrieve scrum tasks from ServiceNow with filtering options for state, assignment group, timeframe, and custom queries to manage agile development workflows.

Instructions

List scrum tasks from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignment_groupNoFilter by assignment group
limitNoMaximum number of records to return
offsetNoOffset to start from
queryNoAdditional query string
stateNoFilter by state
timeframeNoFilter by timeframe (upcoming, in-progress, completed)

Implementation Reference

  • Main handler function for the 'list_scrum_tasks' tool. Validates parameters using ListScrumTasksParams, builds ServiceNow query based on filters like state, assignment_group, timeframe, makes GET request to /api/now/table/rm_scrum_task, and returns list of scrum tasks.
    def list_scrum_tasks(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        List scrum tasks from ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for listing scrum tasks.
    
        Returns:
            A list of scrum tasks.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            ListScrumTasksParams
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Build the query
        query_parts = []
        
        if validated_params.state:
            query_parts.append(f"state={validated_params.state}")
        if validated_params.assignment_group:
            query_parts.append(f"assignment_group={validated_params.assignment_group}")
        
        # Handle timeframe filtering
        if validated_params.timeframe:
            now = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
            if validated_params.timeframe == "upcoming":
                query_parts.append(f"start_date>{now}")
            elif validated_params.timeframe == "in-progress":
                query_parts.append(f"start_date<{now}^end_date>{now}")
            elif validated_params.timeframe == "completed":
                query_parts.append(f"end_date<{now}")
        
        # 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/rm_scrum_task"
        
        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
            scrum_tasks = result.get("result", [])
            count = len(scrum_tasks)
            
            return {
                "success": True,
                "scrum_tasks": scrum_tasks,
                "count": count,
                "total": count,  # Use count as total if total is not provided
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error listing stories: {e}")
            return {
                "success": False,
                "message": f"Error listing stories: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema/parameters for the list_scrum_tasks tool, including pagination (limit, offset), filters (state, assignment_group, timeframe, query).
    class ListScrumTasksParams(BaseModel):
        """Parameters for listing scrum tasks."""
    
        limit: Optional[int] = Field(10, description="Maximum number of records to return")
        offset: Optional[int] = Field(0, description="Offset to start from")
        state: Optional[str] = Field(None, description="Filter by state")
        assignment_group: Optional[str] = Field(None, description="Filter by assignment group")
        timeframe: Optional[str] = Field(None, description="Filter by timeframe (upcoming, in-progress, completed)")
        query: Optional[str] = Field(None, description="Additional query string")
  • Tool registration in the get_tool_definitions() function's tool_definitions dict. Maps 'list_scrum_tasks' to the aliased handler function, input schema (ListScrumTasksParams), return type hint, description, and serialization method ('json').
    "list_scrum_tasks": (
        list_scrum_tasks_tool,
        ListScrumTasksParams,
        str,  # Expects JSON string
        "List scrum tasks from ServiceNow",
        "json",  # Tool returns list/dict
    ),
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. 'List' implies a read operation, but the description doesn't disclose behavioral traits like pagination behavior (implied by limit/offset parameters), authentication requirements, rate limits, or what happens when no tasks match filters. It mentions the source system but provides no operational context.

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 appropriately sized for a list operation and front-loads the essential information (verb + resource + source). Every word earns its place.

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 list tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'scrum tasks' are in ServiceNow context, what fields are returned, how results are ordered, or error conditions. The agent must rely entirely on the input schema for parameter understanding.

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 parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

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 scrum tasks from ServiceNow' clearly states the verb ('List') and resource ('scrum tasks'), but it's vague about scope and doesn't distinguish from sibling tools like 'list_stories' or 'list_epics' that also list ServiceNow entities. It specifies the source ('from ServiceNow') which is helpful context.

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 about when to use this tool versus alternatives. With many sibling list tools (list_stories, list_epics, list_incidents, etc.), the description doesn't explain what makes scrum tasks distinct or when they should be listed versus other entity types.

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