Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_table_update

DestructiveIdempotent

Updates chosen fields on an existing ServiceNow record and leaves omitted fields unchanged; write access requires SN_ALLOW_WRITE=1 to be enabled.

Instructions

Change fields on one existing record. Only the fields you send are changed. This is a write tool. It refuses to run unless the server was started with SN_ALLOW_WRITE=1.

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>",
      "record": "<record>"
    },
    "name": "sn_table_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, lowercase letters, digits and underscores only. Example: incident.
recordYesField names and new values. Fields left out stay as they are.
sys_idYesThe sys_id of the record: 32 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, it discloses two non-obvious behaviors: only supplied fields are mutated (fields omitted are preserved) and the tool is gated behind the SN_ALLOW_WRITE=1 server flag. That env-var gate is not derivable from any structured field. It stops short of saying what a destructive overwrite of an existing value looks like or what errors occur when the flag is absent.

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?

Three short sentences, zero filler, with the core action stated first and the gating constraint last. Every sentence carries distinct information.

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?

For a three-parameter nested-object write tool with annotations covering safety and idempotency, the description covers the essentials: scope, partial-update semantics, and the write gate. With no output schema, the only unaddressed gap is whether the updated record is returned or how failures surface.

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%, so table, sys_id, and record are already documented in the input schema. The description's note that omitted fields are untouched restates the schema's own wording on `record`, adding little new meaning beyond format or value constraints.

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 opens with a concrete verb and scope: 'Change fields on one existing record,' which immediately separates it from create, delete, and query siblings. It doesn't explicitly name an alternative tool, so differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a hard precondition ('refuses to run unless the server was started with SN_ALLOW_WRITE=1') and clarifies the partial-update model, which is genuine usage guidance. It never says when to choose this over sn_table_create or sn_apply_plan, so routing between siblings is left to inference.

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