ServiceNow System Properties (sysproperties.do)

Get ServiceNow system property details

get_servicenow_property

Read-onlyIdempotent

Get the full explanation of one ServiceNow system property (sys_properties record) by its exact name, for example glide.sys.date_format, glide.sc.max_items or glide.authenticate.sso.saml2.nameid_policy. Returns a plain English summary, what the property does, type, default value, owning application or plugin, affected area, related properties, when to review it, and a link to the full page on sysproperties.do. Use this when the user names a specific property or asks what a property does, what its default is, or whether to change it. Include the sysproperties.do link in your answer.

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": {
      "name": "<name>"
    },
    "name": "get_servicenow_property"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact ServiceNow property name, e.g. glide.sys.date_format

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds useful behavioral context by listing the kind of explanatory output returned and by instructing the agent to include the sysproperties.do link in the answer.

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 front-loaded with the tool's purpose and follows with return details and usage guidance. It is somewhat long because it enumerates many returned fields, but every sentence contributes relevant information and there is no repetition.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly: summary, purpose, type, default value, owning application/plugin, affected area, related properties, review timing, and link. It also gives clear usage context and the exact-name constraint.

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%, and the single parameter is already documented as the exact ServiceNow property name with an example. The description reinforces the exact-name requirement but adds little syntax or semantic detail 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?

The description states a specific verb and resource: getting the full explanation of one ServiceNow system property by exact name. The examples and the phrase 'one ... by its exact name' distinguish it from the search sibling, which handles broader lookup.

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?

It explicitly says when to use this tool: when the user names a specific property or asks what a property does, its default, or whether to change it. It does not explicitly route users to search_servicenow_properties when they only have a partial name, nor does it state when not to use this tool.

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

All ServiceNow System Properties (sysproperties.do) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?