Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_create_user

Creates a new Active Directory user account in a specified organizational path, using SAM account name plus optional identity, email, and password attributes.

Instructions

[Users] [WRITE] Criar novo usuario no Active Directory.

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": {
      "sam_account_name": "<sam_account_name>",
      "path": "<path>"
    },
    "name": "ad_create_user"
  }
}

Input Schema

Name	Required	Description	Default
`mail`	No
`name`	No
`path`	Yes
`dry_run`	No
`enabled`	No
`surname`	No
`password`	No
`given_name`	No
`display_name`	No
`correlation_id`	No
`sam_account_name`	Yes
`confirmation_token`	No
`user_principal_name`	No
`password_never_expires`	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.4/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 burden, and the only disclosure is the [WRITE] tag. It says nothing about the dry_run and confirmation_token safeguards that appear in the schema, nor about permission requirements, password handling, irreversibility of account creation, or duplicate-account behavior.

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

Conciseness3/5

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

A single front-loaded sentence with tag prefixes, so nothing is wasted. But the brevity is under-specification rather than efficiency: 14 parameters and a write operation are covered by nine words.

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 needn't be explained, but this is a 14-parameter privileged write operation with zero annotations and zero schema descriptions. The description should at minimum explain dry_run, confirmation_token, and the required path/sam_account_name pairing; it explains none.

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 14 parameters and the description adds no parameter meaning whatsoever. Critical semantics — what 'path' means, that sam_account_name is the required logon key, how dry_run/confirmation_token gate execution, password_never_expires implications — are undocumented in both places.

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 ('Criar novo usuario no Active Directory') and the [Users]/[WRITE] tags make the domain and mutating nature explicit, clearly separating it from ad_update_user, ad_delete_user, and the ad_get_*/ad_list_* readers. The purpose is unmistakable, though no sibling is named and the description is in Portuguese while sibling names are English.

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 use this versus ad_create_computer, ad_create_group, or how it relates to ad_update_user for existing accounts. Nothing states prerequisites (target OU existence, required permissions) or what to do first.

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

Deploy Server