Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_scrum_task

Create a new scrum task in ServiceNow by specifying the story, description, priority, hours, and assignment details to track agile development work items.

Instructions

Create a new scrum task in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigned_toNoUser assigned to the scrum task
assignment_groupNoGroup assigned to the scrum task
descriptionNoDetailed description of the scrum task
hoursNoActual Hours for the scrum task
planned_hoursNoPlanned hours for the scrum task
priorityNoPriority of scrum task (1 is Critical, 2 is High, 3 is Moderate, 4 is Low)
remaining_hoursNoRemaining hours for the scrum task
short_descriptionYesShort description of the scrum task
stateNoState of scrum task (-6 is Draft,1 is Ready, 2 is Work in progress, 3 is Complete, 4 is Cancelled)
storyYesShort description of the story. It requires the System ID of the story.
typeNoType of scrum task (1 is Analysis, 2 is Coding, 3 is Documentation, 4 is Testing)
work_notesNoWork notes to add to the scrum task

Implementation Reference

  • The main handler function that implements the logic for creating a scrum task in ServiceNow, including parameter validation, API request preparation, and execution.
    def create_scrum_task(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Create a new scrum task in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for creating the scrum task.
    
        Returns:
            The created scrum task.
        """
    
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            CreateScrumTaskParams, 
            required_fields=["short_description", "story"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "story": validated_params.story,
            "short_description": validated_params.short_description,
        }
    
        # Add optional fields if provided
        if validated_params.priority:
            data["priority"] = validated_params.priority
        if validated_params.planned_hours:
            data["planned_hours"] = validated_params.planned_hours
        if validated_params.remaining_hours:
            data["remaining_hours"] = validated_params.remaining_hours
        if validated_params.hours:
            data["hours"] = validated_params.hours
        if validated_params.description:
            data["description"] = validated_params.description
        if validated_params.type:
            data["type"] = validated_params.type
        if validated_params.state:
            data["state"] = validated_params.state
        if validated_params.assignment_group:
            data["assignment_group"] = validated_params.assignment_group
        if validated_params.assigned_to:
            data["assigned_to"] = validated_params.assigned_to
        if validated_params.work_notes:
            data["work_notes"] = validated_params.work_notes
        
        # 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",
            }
        
        # Add Content-Type header
        headers["Content-Type"] = "application/json"
        
        # Make the API request
        url = f"{instance_url}/api/now/table/rm_scrum_task"
        
        try:
            response = requests.post(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Scrum Task created successfully",
                "scrum_task": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error creating scrum task: {e}")
            return {
                "success": False,
                "message": f"Error creating scrum task: {str(e)}",
            }
  • Pydantic model defining the input parameters and validation schema for the create_scrum_task tool.
    class CreateScrumTaskParams(BaseModel):
        """Parameters for creating a scrum task."""
    
        story: str = Field(..., description="Short description of the story. It requires the System ID of the story.")
        short_description: str = Field(..., description="Short description of the scrum task")
        priority: Optional[str] = Field(None, description="Priority of scrum task (1 is Critical, 2 is High, 3 is Moderate, 4 is Low)")
        planned_hours: Optional[int] = Field(None, description="Planned hours for the scrum task")
        remaining_hours: Optional[int] = Field(None, description="Remaining hours for the scrum task")
        hours: Optional[int] = Field(None, description="Actual Hours for the scrum task")
        description: Optional[str] = Field(None, description="Detailed description of the scrum task")
        type: Optional[str] = Field(None, description="Type of scrum task (1 is Analysis, 2 is Coding, 3 is Documentation, 4 is Testing)")
        state: Optional[str] = Field(None, description="State of scrum task (-6 is Draft,1 is Ready, 2 is Work in progress, 3 is Complete, 4 is Cancelled)")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the scrum task")
        assigned_to: Optional[str] = Field(None, description="User assigned to the scrum task")
        work_notes: Optional[str] = Field(None, description="Work notes to add to the scrum task")
  • The registration entry in the tool_definitions dictionary that maps the tool name to its handler, schema, return type, description, and serialization method for MCP server integration.
    "create_scrum_task": (
        create_scrum_task_tool,
        CreateScrumTaskParams,
        str,
        "Create a new scrum task in ServiceNow",
        "str",
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create' which implies a write/mutation operation, but doesn't mention required permissions, whether the creation is reversible, what happens on failure, or what the response contains. For a 12-parameter creation tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 that states exactly what the tool does without any wasted words. It's appropriately sized for a tool with comprehensive schema documentation and gets straight to the point with zero 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?

For a creation tool with 12 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation (return values, success indicators), doesn't mention required permissions or constraints, and provides no context about how this fits into the broader ServiceNow scrum workflow. The agent would need to guess about important behavioral aspects.

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%, with each parameter well-documented in the schema itself (including descriptions of what each field represents and enum values for priority, state, and type). The description adds no additional parameter information beyond what's already in the structured schema, so it meets but doesn't exceed the baseline expectation.

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

Purpose4/5

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

The description clearly states the verb ('Create') and resource ('new scrum task in ServiceNow'), making the purpose immediately understandable. It distinguishes from siblings like 'update_scrum_task' by specifying creation rather than modification. However, it doesn't explicitly differentiate from other creation tools like 'create_story' or 'create_incident' within the same domain.

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 prerequisites (e.g., needing an existing story), when this tool is appropriate versus other task management methods, or what distinguishes it from sibling tools like 'create_story' or 'update_scrum_task'. The agent must infer usage from the tool 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