Skip to main content
Glama
Sign In
Microsoft Active Directory MCP Server

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_delete_computer

Deletes a computer account from Active Directory to remove stale or unauthorized devices, with optional dry-run and confirmation controls before destructive changes.

Instructions

[Computers & Devices] [DESTRUCTIVE] Excluir conta de computador.

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": {
      "identity": "<identity>"
    },
    "name": "ad_delete_computer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
identityYes
correlation_idNo
confirmation_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. The [DESTRUCTIVE] marker usefully warns of an irreversible operation, but nothing is said about required permissions, whether a confirmation token is mandatory, what happens to the computer object and its group memberships, or whether dry_run is available as a safety path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, but it is short through under-specification rather than efficiency. The bracketed tags are front-loaded, yet no actionable content follows them.

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

Completeness2/5

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

An output schema exists so return values need not be described, but for a destructive four-parameter mutation with zero annotation coverage, the description omits everything an agent needs: the confirmation/dry-run workflow, identity formats, and blast radius. It is not sufficient to invoke this tool safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description mentions none of them. Critically, dry_run and confirmation_token are safety-critical controls that go entirely unexplained, and identity's accepted formats (DN, GUID, SAM account name) are never stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Excluir conta de computador" names a verb (delete) and resource (computer account), and the [Computers & Devices] tag places it in a domain. But it is essentially a Portuguese restatement of the tool name ad_delete_computer, with no additional distinguishing detail versus siblings like ad_delete_user or ad_delete_group beyond the noun.

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 guidance on when to delete versus disable a computer (ad_disable_computer is a direct sibling), no prerequisites, and no mention of how to handle dependent objects. The only signal is the [DESTRUCTIVE] tag, which hints at caution but does not route the agent to an alternative.

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