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

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_create_gpo

Creates a new Group Policy Object in Active Directory for centralized policy management, with optional comment and dry-run validation.

Instructions

[Group Policy Objects] [WRITE] Criar nova GPO.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
commentNo
dry_runNo
correlation_idNo
confirmation_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 burden, yet it only contributes the '[WRITE]' marker. It does not say whether creation is reversible, what permissions are required, what happens if the name already exists, or what the confirmation_token gates — despite the schema implying a two-step confirmation safety flow.

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?

The single-line fragment is tight but not front-loaded with any useful content beyond category tags; brevity here reflects under-specification rather than efficiency. There is no wasted text, but almost no text at all.

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 write operation with zero annotation coverage and five undocumented parameters, the description is far too thin; the presence of an output schema excuses explaining return values but not the missing mutation semantics, confirmation flow, or failure behavior.

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% and the description explains none of the five parameters. Critical fields such as dry_run, confirmation_token and correlation_id are left completely undefined, and even the required 'name' is only implicitly guessable from the tool purpose.

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 ('Criar nova GPO' / create new GPO) and tags the domain '[Group Policy Objects]' plus '[WRITE]', which separates it from ad_get_gpo, ad_list_gpos, ad_update_gpo and ad_delete_gpo. It does not name any sibling or scope condition, so it stops short of full differentiation.

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_update_gpo/ad_link_gpo, no prerequisites (target domain/DC, permissions), and no explanation of the dry_run/confirmation_token workflow. The agent must infer everything from the tool name.

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