Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_attachment_delete

Destructive

Delete a single ServiceNow attachment by sys_id when write access is enabled; the action is permanent and cannot be undone.

Instructions

Delete one attachment from ServiceNow. 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": {
      "sys_id": "<sys_id>"
    },
    "name": "sn_attachment_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
sys_idYesThe sys_id of the attachment to delete: 32 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description earns credit for adding genuinely new context: irreversibility ('This cannot be undone') and the operational prerequisite that the server must have been started with SN_ALLOW_WRITE=1. It stops short of mentioning permissions or what a failure response looks like, so it is strong rather than exhaustive.

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?

Four short front-loaded sentences: action, irreversibility, tool class, runtime gate. Nothing is padded and the destructive warning arrives before any prerequisites.

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 single-parameter destructive tool with annotations covering the safety profile, the definition covers action, reversibility, and the write-enablement gate. The only gap is that no output schema exists and the description says nothing about what a successful delete returns or how errors 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 description coverage is 100% and the schema already explains sys_id as 32 hex characters; the description only restates that exactly one attachment is targeted. Baseline 3 is appropriate since the schema carries parameter meaning.

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?

States a specific verb and resource ('Delete one attachment from ServiceNow') with an explicit cardinality scope ('one'), which cleanly separates it from sn_attachment_list, sn_attachment_download, and sn_attachment_upload.

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 write-gate sentence tells the agent a precondition for use, but there is no guidance on when to choose deletion versus other attachment operations or how to obtain the sys_id (e.g., via sn_attachment_list). Usage is implied rather than directed.

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