ServiceNow MCP Server

Overview Schema Source Related Servers Discussions Admin

Get System Properties

get_system_properties

Read-onlyIdempotent

Query ServiceNow system properties to inspect configuration settings, filter by name or pattern, and limit results for targeted lookups.

Instructions

Query ServiceNow system properties

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of properties to return
`query`	No	Filter query (e.g., 'name=glide.servlet.uri' or 'nameLIKEglide')

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`truncated`	No
`properties`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.2Oct 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "properties": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "count",
+    "properties"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.7.0Sep 9, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedv0.5.1Aug 1, 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 non-destructive behavior, so the safety profile is fully covered. The description adds nothing beyond that — no hint about result volume, what kinds of properties are returned, or whether pagination matters at the 100-item cap.

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 short sentence with no filler, and the resource is front-loaded. Its brevity is appropriate, though it is terse to the point of leaving usage entirely to structured fields.

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 cover the safety profile, so the return-value and risk story need not be in the description. Still, for a query tool with filtering, a short note on what system properties are or when to reach for it would complete the picture.

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 both the limit and query parameters are fully documented in the schema, including an example filter syntax. The description adds no parameter meaning of its own, which is the expected baseline when the schema does the heavy lifting.

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 names a specific verb (Query) and resource (ServiceNow system properties), which is more precise than the title alone. It does not distinguish this tool from read-oriented siblings such as list_records, get_record, or get_table_schema, so an agent gets clarity but no differentiation.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites, permissions, or common query patterns. The filter format lives only in the schema, not in the description.

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