Skip to main content
Glama
jschuller

ServiceNow MCP Server

by jschuller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete Record

delete_record
DestructiveIdempotent

Delete a record from a ServiceNow table using its sys_id. Specify the table name and sys_id to remove the record.

Instructions

Delete a record from a ServiceNow table by sys_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sys_idYesThe sys_id of the record to delete
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: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

The description goes beyond annotations by explaining the behavior of the confirm parameter, including the server condition and when it is ignored. It does not disclose other side effects (e.g., permanent deletion, cascade effects) but annotations already mark it as destructive.

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 concise purpose statement plus a brief, necessary clarification of the confirm parameter. No redundant information or unnecessary detail.

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 simple destructive operation, the description covers purpose, key parameters, and a behavioral nuance. It omits failure/return behavior, but this is acceptable given the absence of an output schema and the tool's straightforward nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions cover table_name and sys_id adequately, and the tool description adds valuable detail about confirm behavior. However, no further semantics are provided for the other two parameters.

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 the action ('delete') and the resource ('a ServiceNow table by sys_id'), fully distinguishing it from sibling tools like list_records, get_record, create_record, and update_record.

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?

The description implies usage for removing a record but does not explicitly state when to prefer it over alternatives (e.g., updating a status flag) or mention any conditions for use. The verb 'delete' is intuitive but not explicit.

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