Skip to main content
Glama

deactivate_user

Destructive

Deactivate (offboard) a ServiceNow user by setting active=false, identified by sys_id, user_name, or email; requires WRITE_ENABLED=true.

Instructions

Deactivate (offboard) a user by setting active=false. 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": {
      "user": "<user>"
    },
    "name": "deactivate_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUser sys_id, user_name, or email

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so safety is covered. The description adds two useful facts beyond that — the state change is an active=false flag (soft offboard, not a delete) and a write-enablement gate. However, for a destructive offboarding mutation it says nothing about side effects such as role or group membership handling, whether it can be reversed, or behavior on an already-inactive user.

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?

Two tight clauses with zero filler; the action and mechanism are front-loaded and the prerequisite follows. Every part earns its place.

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

Completeness3/5

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

For a single-parameter destructive mutation with no output schema, the mechanism and write gate are the essentials and both are present. Gaps remain around loss of access scope, side effects on the user's existing assignments, and error/already-inactive behavior, which matter for a destructive offboarding tool.

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?

Only one parameter exists and schema description coverage is 100%, with the schema already enumerating the accepted identifier forms (sys_id, user_name, email). The description adds no additional meaning about that argument, so the baseline 3 applies.

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?

States a specific verb and resource ('Deactivate (offboard) a user') plus the exact mechanism ('setting active=false'), so the agent knows precisely what changes. It does not name or contrast with siblings like update_user or create_user, which is the only thing keeping it from a 5.

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?

Gives one real precondition that governs invocation: WRITE_ENABLED=true must be set. It offers no when-to-use guidance relative to alternatives (e.g., using update_user to flip active) and no note on when deactivation is inappropriate versus deletion.

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