Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_search_users

Search directory users by name, login, email, or attribute to locate accounts for administration, auditing, and access checks.

Instructions

[Users] [READ] Pesquisar usuarios por nome, login, e-mail ou atributo.

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": {
      "query": "<query>"
    },
    "name": "ad_search_users"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`correlation_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden; the explicit [READ] tag does at least confirm this is a non-mutating operation, which is genuinely useful. Beyond that it discloses nothing about matching semantics (substring vs exact, wildcards), the default limit of 50 / truncation behavior, or required directory permissions.

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?

A single tight sentence with the resource and searchable fields front-loaded and no filler. It is efficient, though the extreme brevity is partly the cause of the gaps elsewhere.

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?

For a 3-parameter read tool with 0% schema coverage and no annotations, the description omits result limits/pagination, correlation_id purpose, and match semantics. The existence of an output schema relieves it of explaining return values, but the invocation-side gaps remain large.

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%, so the description must compensate, and it partially does by explaining that 'query' matches name, login, e-mail, or attribute. The 'limit' and 'correlation_id' parameters get no explanation whatsoever, leaving two of three parameters undocumented in both schema and description.

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 ('Pesquisar usuarios') and enumerates the searchable attributes (nome, login, e-mail, atributo). However, it never distinguishes itself from close siblings such as ad_list_users or ad_get_user, so an agent must infer that this is the attribute-based lookup rather than the enumeration tool.

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?

No when-to-use guidance at all: nothing says to prefer this over ad_list_users when you have a partial identifier, nor what happens with ambiguous or empty queries. The [Users] [READ] tags only categorize the tool, they don't route the agent.

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

Deploy Server