Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

create_incident

Create a new incident in ServiceNow by specifying key details such as short description, priority, impact, and assignment group for efficient issue tracking and resolution.

Instructions

Create a new incident in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The core handler function that executes the create_incident tool by posting data to the ServiceNow incident table API.
    def create_incident(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: CreateIncidentParams,
    ) -> IncidentResponse:
        """
        Create a new incident in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for creating the incident.
    
        Returns:
            Response with the created incident details.
        """
        api_url = f"{config.api_url}/table/incident"
    
        # Build request data
        data = {
            "short_description": params.short_description,
        }
    
        if params.description:
            data["description"] = params.description
        if params.caller_id:
            data["caller_id"] = params.caller_id
        if params.category:
            data["category"] = params.category
        if params.subcategory:
            data["subcategory"] = params.subcategory
        if params.priority:
            data["priority"] = params.priority
        if params.impact:
            data["impact"] = params.impact
        if params.urgency:
            data["urgency"] = params.urgency
        if params.assigned_to:
            data["assigned_to"] = params.assigned_to
        if params.assignment_group:
            data["assignment_group"] = params.assignment_group
    
        # Make request
        try:
            response = requests.post(
                api_url,
                json=data,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", {})
    
            return IncidentResponse(
                success=True,
                message="Incident created successfully",
                incident_id=result.get("sys_id"),
                incident_number=result.get("number"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to create incident: {e}")
            return IncidentResponse(
                success=False,
                message=f"Failed to create incident: {str(e)}",
            )
  • Pydantic model defining the input parameters for the create_incident tool.
    class CreateIncidentParams(BaseModel):
        """Parameters for creating an incident."""
    
        short_description: str = Field(..., description="Short description of the incident")
        description: Optional[str] = Field(None, description="Detailed description of the incident")
        caller_id: Optional[str] = Field(None, description="User who reported the incident")
        category: Optional[str] = Field(None, description="Category of the incident")
        subcategory: Optional[str] = Field(None, description="Subcategory of the incident")
        priority: Optional[str] = Field(None, description="Priority of the incident")
        impact: Optional[str] = Field(None, description="Impact of the incident")
        urgency: Optional[str] = Field(None, description="Urgency of the incident")
        assigned_to: Optional[str] = Field(None, description="User assigned to the incident")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the incident")
  • Registration of the create_incident tool in the tool definitions dictionary, mapping name to function, schema, return type, description, and serialization method.
    "create_incident": (
        create_incident_tool,
        CreateIncidentParams,
        str,
        "Create a new incident in ServiceNow",
        "str",
    ),
  • Import and alias of the create_incident function as create_incident_tool for use in tool registration.
        create_incident as create_incident_tool,
    )
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. While 'Create' implies a write/mutation operation, the description doesn't disclose important behavioral traits like required permissions, whether this is an idempotent operation, what happens on failure, or what the typical response looks like. This leaves significant gaps for an agent to understand how to use this tool effectively.

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, front-loading the essential information without any wasted words. It follows a clear subject-verb-object structure that immediately communicates the core purpose.

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 10 parameters, no annotations, no output schema, and 0% schema description coverage, the description is severely inadequate. It doesn't explain what constitutes a valid incident, what fields are required beyond 'short_description', what the tool returns, or any error conditions. The agent would struggle to use this tool correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides zero information about parameters, while the schema has 0% description coverage (the schema only has titles, not descriptions). With 10 parameters in the schema and no parameter guidance in the description, this creates a significant knowledge gap about what each parameter means and how they should be used together.

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 incident in ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other incident-related tools like 'update_incident' or 'resolve_incident' that also exist in the sibling tool list, which prevents a perfect score.

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 like 'update_incident' or 'resolve_incident' from the sibling list. It also doesn't mention prerequisites, dependencies, or any context about when incident creation is appropriate versus other operations.

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

Related 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/echelon-ai-labs/servicenow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server