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

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_get_domain_admins

Retrieves members of the Active Directory Domain Admins group for security auditing. Use it to review privileged accounts and verify administrative access.

Instructions

[Security & Audit] [READ] Consultar membros do grupo Domain Admins.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ad_get_domain_admins"
  }
}

Input Schema

NameRequiredDescriptionDefault
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 inline "[READ]" tag does signal a non-destructive read, which is worth some credit, but nothing is said about the elevated permissions typically needed to enumerate Domain Admins, whether nested members are included, or any rate/scale concerns.

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?

One short sentence with the category and read tag front-loaded ahead of the core action. Minimal waste, though the bracketed tags carry little operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 need not be explained, and the tool takes effectively no meaningful input. What is missing is the operational context an agent needs for a privileged-enumeration call: permission requirements and whether the result is direct members only or transitive.

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% and the single parameter (correlation_id) is never mentioned in the description. It is an optional, generic tracing parameter, which limits the harm, but the description still adds no meaning beyond the bare schema.

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 ("Consultar") and a specific resource ("membros do grupo Domain Admins"), so an agent knows exactly what it retrieves. It does not differentiate from overlapping siblings such as ad_list_group_members or ad_get_privileged_users, so it stays below the top band.

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_list_group_members, ad_get_group, or ad_get_privileged_users, which can plausibly return the same information. No prerequisites (e.g., required privileges to enumerate Domain Admins) are mentioned.

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