Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_list_service_accounts

Lists Active Directory service accounts, including gMSAs and accounts with “svc” in the name, with optional filtering and target domain controller selection.

Instructions

List service accounts (gMSAs and accounts with "svc" in name)

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

Input Schema

NameRequiredDescriptionDefault
filterNoAdditional filter pattern (optional)
targetNoTarget DC to run against (e.g., "DC1", "DC2"). Omit to use default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The built-in discovery rule based on gMSAs and "svc" in account names is useful behavioral detail, and "List" suggests a read operation. With no annotations or output schema, however, the description does not explicitly establish read-only behavior, required privileges, result shape, or relevant execution limitations.

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?

The description is a single compact statement with the operation first and the non-obvious account-selection rule immediately afterward. It contains no redundant or distracting wording.

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?

For a simple operation with two fully described optional parameters, the stated scope is sufficient for a basic invocation. It remains minimally complete rather than comprehensive because output, permission requirements, and guidance for broader account searches are absent.

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%, so both optional parameters are already documented, including the default-DC behavior for target. The description adds no further explanation of filter syntax or how filter interacts with the built-in service-account criteria, making the baseline score appropriate.

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—listing service accounts—and clarifies that this includes gMSAs and accounts with "svc" in the name. That scope is clear, but it does not explicitly distinguish the tool from the more general ad_ldap_query sibling.

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 account-selection criteria imply when to use the tool: discovering likely service accounts rather than performing an arbitrary directory lookup. There is no explicit guidance on when to prefer ad_ldap_query or another sibling for broader or differently filtered searches.

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