Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_move_computer

Moves an Active Directory computer object to a different organizational unit (OU) using its identity and target path, with optional dry-run and confirmation controls.

Instructions

[Computers & Devices] [WRITE] Mover computador entre OUs.

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>",
      "target_path": "<target_path>"
    },
    "name": "ad_move_computer"
  }
}

Input Schema

Name	Required	Description	Default
`dry_run`	No
`identity`	Yes
`target_path`	Yes
`correlation_id`	No
`confirmation_token`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

C2.7/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 behavioral-disclosure burden. It marks the operation as [WRITE] and says it moves a computer between OUs, but it does not explain required permissions, whether the move is reversible, how dry_run or confirmation_token affect execution, or what side effects occur.

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?

The description is a single front-loaded sentence with category and write tags, containing no filler. Its brevity is efficient, though it is under-specified rather than fully concise for a mutation tool with five parameters.

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 do not need to be described. However, for a mutation tool with no annotations and 0% parameter description coverage, the definition omits critical invocation context such as dry-run behavior, confirmation requirements, and the distinction from ad_move_object.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only indirectly maps 'computer' and 'OUs' to identity and target_path, while dry_run, correlation_id, and confirmation_token remain unexplained in both schema and description.

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?

The description states a specific verb and resource: moving a computer between OUs, reinforced by the [Computers & Devices] [WRITE] tags. It is clear what the tool does, but it does not distinguish itself from the sibling ad_move_object, which likely has overlapping scope.

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 explicit guidance on when to use this tool versus alternatives such as ad_move_object, nor any prerequisites, constraints, or when-not-to-use conditions. The agent must infer usage solely from the tool name and one-line purpose.

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

Deploy Server