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_user

Retrieve details for a specific Active Directory user by identity to inspect account attributes and directory properties for administration or auditing.

Instructions

[Users] [READ] Consultar detalhes de um usuario.

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

Input Schema

NameRequiredDescriptionDefault
identityYes
propertiesNo
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden, yet it only conveys read nature via the [READ] tag. It says nothing about required permissions, error behavior for missing users, or whether partial property selection affects the result.

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

Conciseness2/5

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

The sentence is short but that brevity stems from under-specification rather than efficiency. The bracketed tags are front-loaded well, but the body carries almost no 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, but with 3 undocumented parameters and zero annotations the definition is missing the essentials an agent needs to call it correctly. The single lookup semantics and identity formats are never stated.

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

Parameters1/5

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

Schema description coverage is 0% and all three parameters (identity, properties, correlation_id) are undocumented in the schema. The description adds no meaning: it doesn't explain what form 'identity' takes (DN, UPN, sAMAccountName) or what 'properties' filters, which are the key decisions for a correct call.

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 ('Consultar') and resource ('detalhes de um usuario'), with [Users] [READ] tags reinforcing scope. It does not distinguish itself from close siblings like ad_search_users or ad_list_users, leaving 'detalhes' ambiguous about what is actually returned.

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 guidance whatsoever about when to use this instead of ad_search_users, ad_list_users, or ad_get_user_groups. The agent must infer that this is a single-object lookup keyed by identity, with no stated prerequisites or exclusions.

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