Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_table_delete

Destructive

Delete one record from a ServiceNow table by table name and sys_id. The action is irreversible and runs only when server write access is explicitly enabled.

Instructions

Delete one record from a ServiceNow table. This cannot be undone. 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>"
    },
    "name": "sn_table_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, lowercase letters, digits and underscores only. Example: incident.
sys_idYesThe sys_id of the record: 32 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the irreversibility is technically redundant but reinforcing. The real added value is the SN_ALLOW_WRITE=1 gate, a non-obvious runtime constraint not expressed in annotations. It omits what happens on a missing sys_id (silent success vs error), which keeps it below a 5.

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?

Four short sentences, front-loaded with the destructive action and consequence. 'This is a write tool' partially restates what annotations and 'Delete' already convey, but it sets up the environment-flag sentence, so it earns its place.

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 two-required-param delete with no output schema, the definition covers action, scope, irreversibility, and the write-enable prerequisite. Only the success/failure response behavior is left unspecified, a minor gap.

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%, with format details for both table and sys_id already documented in the schema (lowercase identifier, 32 hex chars). The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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 ('Delete one record from a ServiceNow table') with explicit single-record scope, which distinguishes it from sibling bulk/mutation tools like sn_table_update and sn_table_create.

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 gives clear operating context and a hard prerequisite (server must be started with SN_ALLOW_WRITE=1), which tells the agent when the call will fail. It does not explicitly name an alternative for bulk deletion or point to query tools for locating sys_ids, so it falls just short of full when/when-not guidance.

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