Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_create_group

Creates a new Active Directory group at a specified path, allowing you to set its name, scope, category, and optional description.

Instructions

[Groups & Members] [WRITE] Criar novo grupo 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": {
      "name": "<name>",
      "path": "<path>"
    },
    "name": "ad_create_group"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`path`	Yes
`dry_run`	No
`description`	No
`group_scope`	No	Global
`correlation_id`	No
`group_category`	No	Security
`sam_account_name`	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.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that this is a write operation that creates a group, without explaining required permissions, conflict behavior, dry_run semantics, confirmation_token usage, or reversibility.

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 no wasted text, and the category/write tags provide quick scanning value. Its brevity is appropriate structurally, though it leaves substantive gaps handled by other dimensions.

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?

For a nine-parameter write tool with no annotations and no schema parameter descriptions, this is not complete enough to guide correct invocation. The output schema reduces the need to explain return values, but permissions, required path format, and safety-related parameters remain unexplained.

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 nine parameters, and the description provides no parameter-level meaning beyond the broad purpose. Important parameters such as path, dry_run, confirmation_token, group_scope, and group_category are undocumented.

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: creating a new group in Active Directory. The [Groups & Members] [WRITE] tags help categorize the operation, but the description does not explicitly differentiate it from sibling tools such as ad_update_group or ad_delete_group.

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?

The description says what the tool does but gives no guidance on when to use it versus alternatives, prerequisites, or exclusions. The [WRITE] tag implies a mutating operation, but no explicit usage conditions are provided.

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

Deploy Server