Skip to main content
Glama
Sign In
ServiceNow Incident MCP Server

ServiceNow Incident MCP Server

by mdasiff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Incident

get_incident

Retrieve a ServiceNow incident by its number to view its details including state, priority, assignment, and timestamps.

Instructions

Retrieve a single ServiceNow incident by its number (e.g. INC0012345). Returns number, state, priority, assignment group, assignee, descriptions and timestamps.

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": "get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
incidentNumberYesServiceNow incident number, e.g. "INC0012345"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided; description specifies that it returns number, state, priority, assignment group, assignee, descriptions, and timestamps. Adequate for a read operation, though error behavior not covered.

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?

Single sentence, front-loaded with action and resource, no wasted words.

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

Completeness5/5

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

Complete for a simple retrieval tool: specifies input (incident number) and output fields, no output schema needed. No missing context.

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 coverage is 100% with parameter description. Description adds an example but does not significantly enhance semantic understanding beyond the schema.

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?

Description clearly states it retrieves a single ServiceNow incident by its number, listing specific fields returned. Clearly distinct from siblings like search_incidents or create_incident.

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

Usage Guidelines4/5

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

Implies usage when incident number is known, but does not explicitly mention alternatives like search_incidents for cases without the number.

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