mcpAD

Find Security Groups

find_security_groups

Read-only

List security-enabled Active Directory groups, optionally filtered by group scope or organizational unit, to target the groups you need.

Instructions

List security-enabled groups (as opposed to distribution groups).

Pass scope to restrict to one group scope: "global", "domain_local" or "universal" (None returns security groups of any scope). Pass base (a DN) to scope to an OU.

Input Schema

Name	Required	Description	Default
`base`	No
`limit`	No
`scope`	No
`domain`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful domain context that only security-enabled groups are returned, but says nothing about result volume, the default limit of 100, or domain behavior across parameters.

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?

Two short paragraphs, front-loaded with the core distinction, then parameter guidance. No wasted sentences.

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 described, and the safety profile is covered by annotations. However, with zero schema description coverage, the undefined 'limit' and 'domain' parameters leave meaningful gaps for an otherwise simple lookup tool.

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 0% across 4 params, so the description must compensate. It does document 'scope' with its three allowed values and 'base' as a DN, but leaves 'limit' and 'domain' entirely unexplained, so half the parameters remain undocumented.

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 ('List security-enabled groups') and immediately distinguishes the concept from distribution groups. It does not name the sibling tool find_distribution_groups or find_groups, but the semantic distinction is clear enough for an agent to choose correctly.

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 description explains how to use the two filtering parameters (scope values, base DN) which implies when to use it, but never states when to prefer this over find_groups or find_distribution_groups, nor any prerequisites. Usage is implied rather than explicit.

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

Deploy Server