Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_incident

Create a new incident in ServiceNow to report and track IT issues or service requests with details like description, priority, category, and assignment information.

Instructions

Create a new incident in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigned_toNoUser assigned to the incident
assignment_groupNoGroup assigned to the incident
caller_idNoUser who reported the incident
categoryNoCategory of the incident
descriptionNoDetailed description of the incident
impactNoImpact of the incident
priorityNoPriority of the incident
short_descriptionYesShort description of the incident
subcategoryNoSubcategory of the incident
urgencyNoUrgency of the incident

Implementation Reference

  • The handler function that executes the create_incident tool, sending a POST request to the ServiceNow incident table API with the provided parameters.
    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 used for MCP server.
    "create_incident": (
        create_incident_tool,
        CreateIncidentParams,
        str,
        "Create a new incident in ServiceNow",
        "str",
    ),
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 for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't mention required permissions, whether this action is reversible, what happens on success/failure, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 for a straightforward creation tool and gets directly to the point without 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 mutation tool with 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what gets returned (incident ID, status, etc.), doesn't mention error conditions or validation rules, and provides no behavioral context. The agent would need to guess about the tool's behavior and output format based solely on the name and parameter schema.

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 clearly documented in the schema itself. The description adds no additional 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 parameter information in the description.

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 target resource ('a new incident in ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other creation tools in the sibling list (like create_article, create_change_request, etc.), which would require specifying what makes incident creation distinct.

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. With sibling tools like 'create_change_request' and 'resolve_incident' available, there's no indication of when an incident is appropriate versus a change request, or whether this should be used for new incidents versus updating existing ones. The agent must infer usage context 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