mcpField
Q
quick-reference

quick-reference

github.com/happy-technologies-llcOther4141 installsUpdated 2d ago
Repository

About quick-reference

A ServiceNow ITSM reference skill for people handling incidents, changes, and problems. It brings common state values, priority rules, fields, queries, and MCP tool operations together for quick lookup.

Key features

  1. 01Incident, change, and problem state tables
  2. 02Impact and urgency priority matrix
  3. 03Encoded query examples
  4. 04Common record field references
  5. 05Incident MCP tool guide
  6. 06Typical ITSM workflow steps

Use cases

  1. 01Look up valid record states
  2. 02Build encoded table queries
  3. 03Check incident priority
  4. 04Follow incident triage and resolution steps

MCP support

Documents ServiceNow MCP tools for querying, creating, assigning, updating, and closing incidents, plus generic table operations.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/happy-technologies-llc/happy-platform-skills --skill quick-reference

After installing, type/quick-referencein Claude Code to confirm it loaded.

Details

From the project README

ITSM Quick Reference

Overview

A quick reference card for common ITSM operations in ServiceNow. Keep this handy for fast lookups of state values, priority matrices, and common query patterns.

  • What problem does it solve? Quick lookup for common ITSM values and operations
  • Who should use this skill? Anyone working with incidents, changes, or problems
  • What are the expected outcomes? Faster development with fewer documentation lookups

Prerequisites

  • Appropriate roles and table access for the operation being performed
  • A confirmed target instance before making changes

Procedure

Incident Operations
Quick Actions
ActionMCP ToolKey Parameters
List incidentsSN-List-Incidentsquery, limit
Create incidentSN-Create-Incidentshort_description, caller_id, category
Update incidentSN-Update-Recordtable_name: incident, sys_id, data
Get incidentSN-Get-Incidentsys_id
Close incidentSN-Close-Incidentsys_id, resolution_code, resolution_notes
Assign incidentSN-Assign-Incidentsys_id, assigned_to, assignment_group
Add work notesSN-Add-Work-Notessys_id, work_notes
Search incidentsSN-Natural-Language-Searchtable: incident, natural language query
Create Incident
Tool: SN-Create-Incident
Parameters:
  short_description: Unable to access email
  description: User reports Outlook not connecting to server
  caller_id: <user_sys_id>
  category: software
  subcategory: email
  impact: 3
  urgency: 3
Close Incident
Tool: SN-Close-Incident
Parameters:
  sys_id: <incident_sys_id>
  resolution_code: Solved (Permanently)
  resolution_notes: Restarted email service and cleared user cache
  close_notes: User confirmed email is working
Assign Incident
Tool: SN-Assign-Incident
Parameters:
  sys_id: <incident_sys_id>
  assigned_to: <user_sys_id>
  assignment_group: <group_sys_id>

State Values

Incident States
ValueLabelDescription
1NewNewly created, not yet triaged
2In ProgressWork has started
3On HoldWaiting for external input
6ResolvedSolution implemented, pending verification
7ClosedVerified and closed
8CanceledCanceled (not applicable)
Change Request States
ValueLabelDescription
-5NewDraft state
-4AssessAssessment phase
-3AuthorizeAwaiting authorization
-2ScheduledApproved and scheduled
-1ImplementImplementation in progress
0ReviewPost-implementation review
3ClosedSuccessfully completed
4CanceledChange canceled
Problem States
ValueLabelDescription
1NewNewly identified
2AssessUnder assessment
3Root Cause AnalysisInvestigating root cause
4Fix in ProgressWorking on permanent fix
5ResolvedRoot cause addressed
6ClosedVerified and closed
7CanceledProblem canceled
Change Types
ValueLabelDescription
standardStandardPre-approved, low risk
normalNormalRequires CAB approval
emergencyEmergencyExpedited approval process

Priority Matrix

Impact x Urgency = Priority
Urgency 1 (High)Urgency 2 (Medium)Urgency 3 (Low)
Impact 1 (High)Priority 1 (Critical)Priority 2 (High)Priority 3 (Moderate)
Impact 2 (Medium)Priority 2 (High)Priority 3 (Moderate)Priority 4 (Low)
Impact 3 (Low)Priority 3 (Moderate)Priority 4 (Low)Priority 5 (Planning)
Priority Values
ValueLabelSLA TargetDescription
1Critical1 hourBusiness critical, widespread impact
2High4 hoursSignificant business impact
3Moderate24 hoursLimited business impact
4Low72 hoursMinor inconvenience
5PlanningNo SLAFuture enhancement

Common Encoded Queries

Incident Queries
DescriptionEncoded Query
Active incidentsactive=true
P1 incidentspriority=1
P1 or P2 incidentspriority=1^ORpriority=2
Unassigned incidentsassigned_toISEMPTY
Assigned incidentsassigned_toISNOTEMPTY
Created todaysys_created_onONToday@javascript:gs.beginningOfToday()@javascript:gs.endOfToday()
Created last 7 dayssys_created_on>=javascript:gs.daysAgoStart(7)
New statestate=1
In Progressstate=2
Resolved or Closedstate=6^ORstate=7
Not Closedstate!=7
My incidentsassigned_to=javascript:gs.getUserID()
My team's incidentsassignment_group=<group_sys_id>
Contains textshort_descriptionLIKEnetwork
Starts withnumberSTARTSWITHINC00100
Category is networkcategory=network
Ordered by priorityORDERBYpriority
Ordered by created (newest)ORDERBYDESCsys_created_on
Change Request Queries
DescriptionEncoded Query
Emergency changestype=emergency
Normal changestype=normal
Standard changestype=standard
Scheduled changesstate=-2
Changes this weekstart_dateONThis week@javascript:gs.beginningOfThisWeek()@javascript:gs.endOfThisWeek()
High risk changesrisk=1
Pending approvalstate=-3^approval!=approved
Problem Queries
DescriptionEncoded Query
Open problemsstate<6
Root cause analysisstate=3
Known errorsknown_error=true
Problems with workaroundworkaroundISNOTEMPTY
Related to incidentsrelated_incidentsISNOTEMPTY

Field Reference

Common Incident Fields
FieldTypeDescription
numberStringAuto-generated (INC0010001)
short_descriptionStringBrief summary (required)
descriptionStringDetailed description
caller_idReferenceReporting user
opened_byReferenceUser who created record
assigned_toReferenceAssigned technician
assignment_groupReferenceAssigned team
stateChoiceCurrent state
impactChoiceBusiness impact (1-3)
urgencyChoiceTime sensitivity (1-3)
priorityChoiceCalculated priority (1-5)
categoryChoiceIncident category
subcategoryChoiceIncident subcategory
work_notesJournalInternal notes
commentsJournalCustomer-visible notes
resolution_codeChoiceHow resolved
resolution_notesStringResolution details
close_codeChoiceClosure reason
close_notesStringClosure notes
cmdb_ciReferenceConfiguration item
Common Change Fields
FieldTypeDescription
numberStringAuto-generated (CHG0010001)
short_descriptionStringBrief summary
descriptionStringDetailed description
typeChoicestandard/normal/emergency
stateChoiceCurrent state
riskChoiceRisk level (1-4)
impactChoiceBusiness impact (1-3)
start_dateDateTimePlanned start
end_dateDateTimePlanned end
requested_byReferenceRequester
assigned_toReferenceChange owner
assignment_groupReferenceOwning team
cab_requiredBooleanNeeds CAB approval
justificationStringBusiness justification
implementation_planStringImplementation steps
backout_planStringRollback procedure
test_planStringTesting steps
Common Problem Fields
FieldTypeDescription
numberStringAuto-generated (PRB0010001)
short_descriptionStringBrief summary
descriptionStringDetailed description
stateChoiceCurrent state
priorityChoicePriority (1-5)
assigned_toReferenceProblem manager
assignment_groupReferenceOwning team
known_errorBooleanIs known error
workaroundStringTemporary workaround
cause_notesStringRoot cause
fix_notesStringPermanent fix
related_incidentsListRelated incidents
cmdb_ciReferenceConfiguration item

Resolution Codes

Incident Resolution Codes
ValueLabel
Solved (Work Around)Temporary fix applied
Solved (Permanently)Root cause addressed
Solved Remotely (Work Around)Remote temporary fix
Solved Remotely (Permanently)Remote permanent fix
Not Solved (Not Reproducible)Cannot reproduce
Not Solved (Too Costly)Fix not cost-effective
Closed/Resolved by CallerUser resolved
Close Codes
ValueLabel
SolvedResolved successfully
Closed/Resolved by CallerUser resolved
Not Solved (Not Reproducible)Cannot reproduce
Closed (Cancelled)Request withdrawn

Category Reference

Incident Categories
CategorySubcategories
hardwarecpu, disk, keyboard, memory, monitor, mouse
softwareemail, operating system, application
networkconnectivity, dhcp, dns, firewall, vpn
databasedb2, ms sql server, oracle
inquiryrequest, password reset

MCP Tools Quick Reference

Incident Tools
ToolPurposeRequired Parameters
SN-List-IncidentsQuery incidents-
SN-Get-IncidentGet single incidentsys_id
SN-Create-IncidentCreate incidentshort_description
SN-Update-RecordUpdate incidenttable_name, sys_id, data
SN-Close-IncidentClose incidentsys_id, resolution_code
SN-Assign-IncidentAssign incidentsys_id
SN-Add-Work-NotesAdd work notessys_id, work_notes
SN-Natural-Language-SearchNL searchtable, query
Generic Tools
ToolPurposeRequired Parameters
SN-Query-TableQuery any tabletable_name
SN-Get-RecordGet any recordtable_name, sys_id
SN-Create-RecordCreate any recordtable_name, data
SN-Update-RecordUpdate any recordtable_name, sys_id, data

Common Workflows

Triage New Incident
1. Query: SN-Query-Table(table_name: incident, query: state=1^active=true)
2. Review: Check short_description, category, caller_id
3. Categorize: SN-Update-Record(table_name: incident, sys_id: X, data: {category: network, subcategory: connectivity}, instance: dev)
4. Prioritize: SN-Update-Record(table_name: incident, sys_id: X, data: {impact: 2, urgency: 2}, instance: dev)
5. Assign: SN-Assign-Incident(sys_id: X, assignment_group: <network_team>)
Escalate Incident
1. Update state: SN-Update-Record(table_name: incident, sys_id: X, data: {state: 2}, instance: dev)
2. Add notes: SN-Add-Work-Notes(sys_id: X, work_notes: Escalating to L2 per procedure)
3. Reassign: SN-Assign-Incident(sys_id: X, assignment_group: <l2_team>)
Resolve Incident
1. Resolve: SN-Resolve-Incident(sys_id: X, resolution_code: Solved (Permanently), resolution_notes: Restarted service, instance: dev)
2. Notify: SN-Add-Work-Notes(sys_id: X, work_notes: Resolution confirmed by user)
Close Incident
1. Close: SN-Close-Incident(sys_id: X, resolution_code: Solved (Permanently), resolution_notes: Service restored, close_notes: Verified with user)

REST API Endpoints

Table API
TableEndpoint
Incident/api/now/table/incident
Change Request/api/now/table/change_request
Problem/api/now/table/problem
Task/api/now/table/task
User/api/now/table/sys_user
Group/api/now/table/sys_user_group
CI/api/now/table/cmdb_ci
Common Parameters
ParameterDescriptionExample
sysparm_queryEncoded queryactive=true^priority=1
sysparm_fieldsFields to returnnumber,short_description,state
sysparm_limitMax records100
sysparm_offsetSkip records50
sysparm_display_valueDisplay valuesall, true, false

Best Practices

  • Query and verify records before updating them.
  • Prefer the narrowest table, field list, and encoded query that satisfies the task.
  • Confirm state and resolution values against the target instance before closing records.

Related Skills

  • itsm/incident-lifecycle - Full incident lifecycle management
  • itsm/incident-triage - Detailed triage procedures
  • itsm/natural-language-queries - Natural language search
  • admin/generic-crud-operations - Detailed CRUD operations

References

Comments

Markdown supported