Skip to main content
Glama

sn_mcp_delete_server

Destructive

Deletes an MCP Server Console server and, by default, its auto-created OAuth client, AutoGen, WDF, ACL, and AI Control Tower records, returning undeletable leftovers with sys_ids.

Instructions

Delete an MCP Server Console server and, by default, the OAuth client, AutoGen provider/alias/connection/credential, WDF mapping, execute ACL and AI Control Tower records ServiceNow created for it. Tool definitions are detached, not deleted. Out-of-box (scoped) servers are refused. Records this user cannot delete (the ACL needs security_admin) are returned as leftovers with sys_ids. REQUIRES WRITE_ENABLED=true.

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": {
      "server": "<server>"
    },
    "name": "sn_mcp_delete_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesServer name, label or sys_id
cleanup_auto_createdNoAlso delete the records ServiceNow auto-created on activation (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by enumerating exactly which records are removed, stating that tool definitions are detached rather than deleted, that scoped servers are refused, that partially-failing records surface as leftovers with sys_ids, and that security_admin ACL rights are needed.

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?

Dense but almost every clause carries distinct operational information, and the primary behavior is front-loaded. The critical WRITE_ENABLED=true gate sits at the very end in caps rather than being surfaced earlier, which slightly hurts scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, cascading delete with no output schema, the definition covers scope, cascade contents, detach-not-delete semantics, refusal cases, partial-failure leftovers, permission requirements, and the environment gate. An agent has everything needed to decide whether to call it and how to interpret the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by spelling out what cleanup_auto_created actually removes (OAuth client, AutoGen provider/alias/connection/credential, WDF mapping, execute ACL, AI Control Tower records) and by confirming the 'by default' semantics of that flag.

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 an MCP Server Console server') with explicit scope (cascade vs. detach), which clearly separates it from siblings like sn_mcp_remove_tool or sn_mcp_unregister_external_server.

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?

Gives clear usage conditions: the default cascade behavior, the refusal of out-of-box scoped servers, and the WRITE_ENABLED=true prerequisite. It does not name an alternative for cases where the caller only wants to detach a server rather than delete it, leaving that inference to the agent.

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