servicenow-mcp-ai

Get ServiceNow record

servicenow_get_record

Read-onlyIdempotent

Retrieve a single ServiceNow table record by its sys_id, optionally limiting returned fields, to inspect exact record data via REST.

Instructions

Read a single record from a table by its sys_id.

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": {
      "table": "<table>",
      "sys_id": "<sys_id>"
    },
    "name": "servicenow_get_record"
  }
}

Input Schema

Name	Required	Description
`table`	Yes	Table, e.g. 'incident'.
`fields`	No	Columns (default all).
`sys_id`	Yes	Record sys_id.
`instance`	No	Profile (default active)
`displayValue`	No	As in query_table.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv3.0.0Oct 21, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / displayValue

Added value: +{
+  "description": "As in query_table.",
+  "enum": [
+    "true",
+    "false",
+    "all",
+    "display"
+  ],
+  "type": "string"
+}

changedInput schema / properties / fields / description

Previous value: -"Columns to return. Omit to return all columns."New value: +"Columns (default all)."

addedInput schema / properties / fields / items / maxLength
```
Added value: +255
```

addedInput schema / properties / fields / items / pattern

Added value: +"^[A-Za-z0-9_.]+(?:\\s*,\\s*[A-Za-z0-9_.]+)*$"

addedInput schema / properties / fields / maxItems
```
Added value: +200
```

changedInput schema / properties / instance / description

Previous value: -"Connection profile to use for this call (default: the active profile). See servicenow_list_instances."New value: +"Profile (default active)"

addedInput schema / properties / instance / maxLength
```
Added value: +128
```

changedInput schema / properties / sys_id / description

Previous value: -"The sys_id of the record to read."New value: +"Record sys_id."

addedInput schema / properties / sys_id / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,32}$"
```

changedInput schema / properties / table / description

Previous value: -"Table name, e.g. 'incident'."New value: +"Table, e.g. 'incident'."

addedInput schema / properties / table / pattern
```
Added value: +"^[A-Za-z0-9_]{1,80}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

First observedv2.0.1Sep 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description adds essentially nothing on the safety profile. It omits useful behavioral context such as what happens when the sys_id does not exist, whether fields default to all columns, and how displayValue affects the payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, so nothing needs trimming. It is efficient but borders on under-specified rather than genuinely concise.

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?

An output schema exists and annotations carry the safety profile, so the thin description is not fatal. Still, for a read tool with five parameters and a common not-found failure mode, one sentence leaves the agent inferring error behavior and field-selection semantics.

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%, so every parameter including fields, instance and displayValue is already documented in the schema. The description only names table and sys_id, adding no syntax or format detail beyond what the schema provides, which matches the baseline 3.

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?

States a specific verb and resource ('Read a single record') plus the scoping mechanism ('from a table by its sys_id'), which is enough to distinguish it from servicenow_query_table's bulk retrieval without opening either schema. It stops short of naming siblings explicitly.

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?

No when-to-use guidance, no exclusions, and no named alternative such as servicenow_query_table. Only the oblique hint 'by its sys_id' suggests the precondition that the caller already knows the identifier.

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