Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_get_user_groups

Lists every Active Directory group a specified user is a direct member of, letting you verify access rights without expanding nested group memberships.

Instructions

Get all groups a user is a direct member of (does not recurse nested groups)

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": {
      "username": "<username>"
    },
    "name": "ad_get_user_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoTarget DC to run against (e.g., "DC1", "DC2"). Omit to use default.
usernameYessAMAccountName of the user

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full disclosure burden. It does disclose one important behavioral trait — that only direct membership is returned and nested groups are excluded — which directly shapes interpretation of results. It does not cover permissions needed, behavior for nonexistent users, or the shape of the returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the resource and the key scoping constraint front-loaded in a parenthetical. No redundant phrasing and nothing an agent must read past to reach the operative detail.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple two-parameter read lookup with fully documented parameters, so the description is close to complete. The notable remaining gap is the return shape — whether groups come back as names, DNs, or objects — which matters because no output schema exists to answer it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both 'username' (sAMAccountName) and 'target' (target DC) documented in the schema itself. The description adds no additional meaning about either parameter, such as accepted formats or domain-qualification rules. Baseline 3 applies when the schema does the work.

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 and resource: 'get all groups a user is a direct member of'. The parenthetical narrows the scope to non-recursive membership, which is a meaningful distinction from a recursive variant. It does not explicitly differentiate itself from any named sibling, though none of the listed siblings appear to cover group membership.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(does not recurse nested groups)' implies a when-not condition: if you need nested membership, this tool will not give it. However, no alternative tool is named for that case, and there is no guidance on prerequisites or context of use. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.