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_group

Deletes a group from Active Directory to remove obsolete or unwanted group objects, with optional dry-run and confirmation safeguards.

Instructions

[Groups & Members] [DESTRUCTIVE] Excluir grupo do 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": {
      "identity": "<identity>"
    },
    "name": "ad_delete_group"
  }
}

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.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 burden, yet it only adds a DESTRUCTIVE marker. It never explains that deletion is irreversible, what dependent memberships are lost, what permissions are required, or that dry_run/confirmation_token exist as safety gates — details that matter enormously for a destructive operation.

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?

A single short sentence with the category and DESTRUCTIVE flag front-loaded — zero padding. It is arguably too terse for a destructive tool, but as a structure/conciseness matter it is efficient.

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 an irreversible delete with no annotations, 0% parameter coverage, and undocumented confirmation/dry-run workflow, the description is far from sufficient. An output schema exists, so return values need no explanation, but the operational contract around a destructive call is missing.

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% across 4 parameters, and the description only implies the 'identity' parameter via the word 'grupo'. The safety-critical dry_run and confirmation_token parameters and the correlation_id are entirely 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?

States a specific verb and resource ('Excluir grupo do Active Directory') plus a category tag and a DESTRUCTIVE marker, so the operation is unambiguous. It does not differentiate from sibling delete tools (ad_delete_user, ad_delete_ou, ad_delete_computer) beyond the noun itself, but the name already carries that distinction.

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 alternatives such as ad_update_group or ad_remove_group_member, and no prerequisites, preconditions, or warnings about irreversibility. The only usage signal is the DESTRUCTIVE tag, which warns but does not instruct.

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