@beyondidentity/mcp

Official

Overview Schema Source Related Servers Discussions Admin

scim_delete_user

Destructive

Delete a SCIM user and remove them from all groups; the operation may be a soft or hard delete depending on configuration.

Instructions

Delete a SCIM user. Removes the user from all groups. May be soft or hard delete depending on configuration.

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_id": "<user_id>"
    },
    "name": "scim_delete_user"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	ID of the user.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the cascading side effect (removal from all groups) and the non-deterministic soft-vs-hard delete behavior driven by configuration, which an agent cannot learn from the annotations or schema.

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?

Three short sentences, front-loaded with the action and followed by the two behavioral facts that matter most. No filler, though the phrasing is clipped rather than polished.

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 delete with no output schema, the description covers the essential behavior: what is removed, the cascading group effect, and the variability of the operation. It omits only secondary details like permission requirements and the response shape after deletion.

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 (user_id) and schema description coverage is 100%, so the schema fully documents it. The description adds nothing about the ID's format or source, 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 ('Delete a SCIM user') and the SCIM qualifier implicitly separates it from the generic delete_user sibling. It also adds scope detail ('Removes the user from all groups'). It stops short of explicitly naming when to prefer it over delete_user, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. With siblings like delete_user, scim_delete_group, and delete_group_users present, the description never clarifies which deletion tool applies to which resource, leaving the agent to infer from the name alone.

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