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_gpo

Retrieve details for a Group Policy Object by identity to inspect its configuration and support directory administration or audit tasks.

Instructions

[Group Policy Objects] [READ] Consultar detalhes de uma 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": {
      "identity": "<identity>"
    },
    "name": "ad_get_gpo"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityYes
correlation_idNo

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 burden. It signals read-only intent via the [READ] tag, but says nothing about required permissions, behavior when the GPO does not exist, or whether identity accepts a name, GUID, or DN. That leaves real operational uncertainty for a tool with zero structured behavioral metadata.

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 bracketed category and mode tags front-loaded; nothing is padded or redundant. However, the brevity comes at the cost of substance rather than from efficiently packing in information.

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?

An output schema exists, so return values need not be described. Still, for a 2-parameter tool with 0% schema coverage and no annotations, the description leaves the identity format and the meaning of correlation_id entirely unresolved, which is the main gap an agent must close before calling it.

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 neither of the two parameters is documented in the schema. The description implies 'identity' identifies the GPO but never states the accepted format (GUID vs. display name vs. DN), and correlation_id is not mentioned at all.

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 gives a specific verb ('Consultar detalhes') and resource ('uma GPO'), tagged with the object class [Group Policy Objects] and the mode [READ]. It is distinguishable from ad_list_gpos and ad_create_gpo/ad_delete_gpo, though it does not explicitly contrast with near-siblings like ad_get_gpo_report or ad_get_gpo_links.

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 statement of when to use this tool versus alternatives. With siblings such as ad_get_gpo_report, ad_get_gpo_links, and ad_compare_gpos in the same family, an agent gets no routing guidance. The [READ] tag implies a non-destructive lookup but nothing more.

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