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

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_disable_user

Disable an Active Directory user account to block sign-in access while preserving the account for later review or re-enablement.

Instructions

[Users] [WRITE] Desabilitar conta de usuario.

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_disable_user"
  }
}

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.6/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. The '[WRITE]' tag conveys mutation and 'disable' implies a reversible state change, but the description says nothing about required permissions, reversibility, or the presence of safety mechanisms (dry_run, confirmation_token) that the schema exposes.

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 front-loaded sentence with the resource tag first and the action second — no filler. Brevity is appropriate in form, though the sentence under-specifies rather than being tight.

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 no annotations, four undocumented parameters, and a confirmation-token workflow, one sentence is insufficient. The existing output schema means return values need not be described, but the agent still lacks the operational context to safely call a destructive-ish AD mutation.

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 four parameters, and the description mentions none of them. The meaning and expected format of 'identity', plus the safety semantics of 'dry_run' and 'confirmation_token', are entirely undocumented anywhere.

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 names a specific verb+resource combination ('Desabilitar conta de usuario') and tags it '[Users] [WRITE]', so an agent can tell it disables a user account rather than deleting or enabling one. It does not explicitly differentiate itself from close siblings like ad_enable_user or ad_delete_user, but the verb is unambiguous on its own.

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 tool versus ad_delete_user, ad_enable_user, or ad_update_user, and no stated prerequisites (e.g., target must exist, must currently be enabled). The agent must infer all selection logic from the name alone.

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