Skip to main content
Glama
jschuller

ServiceNow MCP Server

by jschuller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Record

update_record
DestructiveIdempotent

Update a ServiceNow record by providing the table name, record sys_id, and field-value pairs. Optionally acknowledge destructive changes with the confirm flag.

Instructions

Update an existing record in a ServiceNow table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesFields to update as key-value pairs
sys_idYesThe sys_id of the record to update
confirmNoAcknowledge this destructive change. Only consulted when the server runs with --write-confirm and the client cannot show a confirmation dialog; ignored otherwise.
table_nameYesThe ServiceNow table name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "Acknowledge this destructive change. Only consulted when the server runs with --write-confirm and the client cannot show a confirmation dialog; ignored otherwise.",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, and the description action 'Update' aligns with those. However, the description itself adds no extra behavioral context, such as side effects, confirmation behavior, or whether the record must already exist.

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?

The description is a single, clear sentence with no filler or redundant information. It efficiently conveys the core purpose.

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?

The description is adequate for a basic update operation, but it omits details about the return value, error behavior, or any post-update effects. Given there is no output schema, some mention of what the caller should expect would improve completeness.

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% with each parameter individually described in the input schema. The tool description adds no extra parameter meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states a specific action ('Update') and resource ('existing record in a ServiceNow table'), which distinguishes it from sibling tools like create_record, get_record, and delete_record without needing to inspect their schemas.

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 guidance is provided about when to prefer this tool over alternatives, such as using create_record for new records or delete_record for removals. It also does not mention the destructive nature or confirmation flow, leaving the agent to infer usage context.

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