Skip to main content
Glama
Sign In
ServiceNow Incident MCP Server

ServiceNow Incident MCP Server

by mdasiff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Assign Incident

assign_incident

Assign a ServiceNow incident to an assignment group or user. Provide the incident number and at least the group or assignee.

Instructions

Set the assignment group and/or assignee on an incident. Provide at least one of assignmentGroup or assignedTo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "incidentNumber": "<incidentNumber>"
    },
    "name": "assign_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
incidentNumberYesServiceNow incident number, e.g. "INC0012345"
assignmentGroupNoAssignment group name
assignedToNoAssignee user_name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided; description only states the action without detailing side effects (e.g., overwrite behavior, notifications, permissions required). For a mutating tool, more transparency is needed.

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?

Two sentences, no fluff. First sentence states purpose, second adds key usage constraint. Ideal conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fairly complete for a simple tool, but missing description of return values or error conditions. Could mention success confirmation or any side effects.

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

Parameters4/5

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

Adds value beyond the schema by clarifying that at least one of assignmentGroup or assignedTo must be provided, which is not enforced by the required array. Schema coverage is 100%, so baseline is 3; the extra constraint warrants a 4.

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

Purpose5/5

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

The description clearly states the verb 'Set' and resource 'assignment group and/or assignee on an incident', distinguishing it from siblings like create_incident, get_incident, and close_incident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides the constraint 'Provide at least one of assignmentGroup or assignedTo', but lacks explicit guidance on when to use this tool versus alternatives like suggest_assignment_group or update_incident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools