servicenow-mcp-ai

Get ServiceNow connection status

servicenow_get_status

Read-onlyIdempotent

Shows ServiceNow profile status: instance, authentication, missing credentials, write mode, policies, limits, TLS, queue, write counters, version, and uptime. Secrets are never shown.

Instructions

Show instance, auth, missing credentials, per-profile write mode, policy, limits, TLS, queue, write counters, version, uptime. Secrets are never shown.

Input Schema

Name	Required	Description	Default
`instance`	No	Profile (default active)

Output Schema

Name	Required	Description	Default
`http`	Yes
`user`	Yes
`policy`	Yes
`server`	Yes
`writes`	Yes
`authMode`	Yes
`instance`	Yes
`profiles`	Yes
`readOnly`	Yes
`telemetry`	Yes
`configured`	Yes
`pluginApis`	Yes
`sdkManaged`	Yes
`passwordSet`	Yes
`authWarnings`	Yes
`deniedTables`	Yes
`activeProfile`	Yes
`allowedTables`	Yes
`deniedPackages`	Yes
`profileDetails`	Yes
`enabledPackages`	Yes
`readOnlyPackages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv3.0.0Oct 21, 2026

removedInput schema / $schema

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

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
```

removedOutput schema / $schema

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

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
removedOutput schema / properties / allowedTables / items
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / authWarnings
```
Added value: +{
+  "type": "array"
+}
```
removedOutput schema / properties / deniedPackages / items
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / deniedTables / items
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / enabledPackages / items
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / http
```
Added value: +{
+  "type": "object"
+}
```
removedOutput schema / properties / pluginApis / additionalProperties
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / policy
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / profileDetails
```
Added value: +{
+  "type": "array"
+}
```
removedOutput schema / properties / profiles / items
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / readOnlyPackages / items
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / sdkManaged
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / server
```
Added value: +{
+  "type": "object"
+}
```
removedOutput schema / properties / telemetry / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / telemetry / properties

Removed value: -{
-  "errors": {
-    "additionalProperties": {
-      "type": "number"
-    },
-    "type": "object"
-  },
-  "perHost": {
-    "additionalProperties": {
-      "additionalProperties": false,
-      "properties": {
-        "errors": {
-          "additionalProperties": {
-            "type": "number"
-          },
-          "type": "object"
-        },
-        "requests": {
-          "type": "number"
-        },
-        "retries": {
-          "type": "number"
-        },
-        "totalMs": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "requests",
-        "retries",
-        "errors",
-        "totalMs"
-      ],
-      "type": "object"
-    },
-    "type": "object"
-  },
-  "requests": {
-    "type": "number"
-  },
-  "retries": {
-    "type": "number"
-  },
-  "totalMs": {
-    "type": "number"
-  }
-}

removedOutput schema / properties / telemetry / required

Removed value: -[
-  "requests",
-  "retries",
-  "errors",
-  "totalMs",
-  "perHost"
-]

addedOutput schema / properties / writes
```
Added value: +{
+  "type": "object"
+}
```

changedOutput schema / required

Previous value: -[
-  "configured",
-  "activeProfile",
-  "profiles",
-  "instance",
-  "user",
-  "passwordSet",
-  "authMode",
-  "readOnly",
-  "allowedTables",
-  "deniedTables",
-  "enabledPackages",
-  "deniedPackages",
-  "readOnlyPackages",
-  "pluginApis",
-  "telemetry"
-]New value: +[
+  "configured",
+  "activeProfile",
+  "profiles",
+  "instance",
+  "user",
+  "passwordSet",
+  "authMode",
+  "authWarnings",
+  "readOnly",
+  "allowedTables",
+  "deniedTables",
+  "enabledPackages",
+  "deniedPackages",
+  "readOnlyPackages",
+  "pluginApis",
+  "telemetry",
+  "http",
+  "sdkManaged",
+  "server",
+  "policy",
+  "writes",
+  "profileDetails"
+]

First observedv2.0.1Sep 5, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context by inventorying exposed fields and explicitly stating that secrets are never shown, which is important for a status tool.

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?

The description is two sentences and contains no filler; the field inventory is dense but purposeful. The secret-disclosure note is front-loaded enough to be noticed, though the long field list is terse rather than explanatory.

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

Completeness4/5

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

With rich annotations, complete schema coverage, and an output schema, the description only needs to summarize scope and special behavior. It does that, including the important 'secrets are never shown' guarantee, though it leaves sibling differentiation unaddressed.

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%, and the single optional parameter is documented as 'Profile (default active).' The description reinforces the profile context via 'per-profile write mode' but does not add syntax or selection details beyond the schema.

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 uses a clear verb, 'Show,' and enumerates the status fields returned, so the purpose is specific and understandable. However, it does not explicitly distinguish this status tool from siblings like servicenow_test_connection or servicenow_check_capabilities.

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 lists what will be shown but gives no explicit guidance on when to use this tool versus alternatives. An agent can infer it is a status/diagnostic tool, but there are no stated exclusions or sibling references.

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