Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_epic

Create a new epic in ServiceNow to organize and track large bodies of work, specifying details like description, priority, state, assignment group, and work notes.

Instructions

Create a new epic in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigned_toNoUser assigned to the epic
assignment_groupNoGroup assigned to the epic
descriptionNoDetailed description of the epic
priorityNoPriority of epic (1 is Critical, 2 is High, 3 is Moderate, 4 is Low, 5 is Planning)
short_descriptionYesShort description of the epic
stateNoState of story (-6 is Draft,1 is Ready,2 is Work in progress, 3 is Complete, 4 is Cancelled)
work_notesNoWork notes to add to the epic. Used for adding notes and comments to an epic

Implementation Reference

  • The core handler function for the 'create_epic' tool. It validates input parameters using CreateEpicParams, constructs the request data, authenticates via auth_manager and server_config, and performs a POST request to the ServiceNow rm_epic table API.
    def create_epic(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Create a new epic in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for creating the epic.
    
        Returns:
            The created epic.
        """
    
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            CreateEpicParams, 
            required_fields=["short_description"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {
            "short_description": validated_params.short_description,
        }
           
        # Add optional fields if provided
        if validated_params.description:
            data["description"] = validated_params.description
        if validated_params.priority:
            data["priority"] = validated_params.priority
        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_epic"
        
        try:
            response = requests.post(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Epic created successfully",
                "epic": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error creating epic: {e}")
            return {
                "success": False,
                "message": f"Error creating epic: {str(e)}",
            }
  • Pydantic model defining the input schema for the create_epic tool, including required short_description and optional fields like description, priority, etc.
    class CreateEpicParams(BaseModel):
        """Parameters for creating an epic."""
    
        short_description: str = Field(..., description="Short description of the epic")
        description: Optional[str] = Field(None, description="Detailed description of the epic")
        priority: Optional[str] = Field(None, description="Priority of epic (1 is Critical, 2 is High, 3 is Moderate, 4 is Low, 5 is Planning)")
        state: Optional[str] = Field(None, description="State of story (-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 epic")
        assigned_to: Optional[str] = Field(None, description="User assigned to the epic")
        work_notes: Optional[str] = Field(None, description="Work notes to add to the epic. Used for adding notes and comments to an epic")
  • Registers the 'create_epic' tool in the MCP tool definitions dictionary within get_tool_definitions(), mapping the name to its handler (create_epic_tool), input schema (CreateEpicParams), return type, description, and serialization method.
    "create_epic": (
        create_epic_tool,
        CreateEpicParams,
        str,
        "Create a new epic in ServiceNow",
        "str",
    ),
  • Imports the create_epic function from epic_tools.py into the tools package namespace, making it available for higher-level registration.
    from servicenow_mcp.tools.epic_tools import (
        create_epic,
        update_epic,
        list_epics,
    )
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. It states 'Create' which implies a write/mutation operation, but doesn't mention permissions required, whether creation is reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is insufficient.

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 the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

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 mutation tool with 7 parameters and no annotations or output schema, the description is inadequate. It doesn't explain what happens after creation, error conditions, or behavioral aspects. The high schema coverage helps with parameters, but overall context is incomplete for a creation operation.

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 the schema already documents all 7 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation when schema does the heavy lifting.

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 action ('Create') and resource ('new epic in ServiceNow'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'create_story' or 'create_change_request', but the specificity is adequate for basic understanding.

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 like 'create_story' or 'create_change_request'. The description states what it does but offers no context about appropriate scenarios, prerequisites, or comparisons to sibling tools.

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