Skip to main content
Glama
fredriksknese

mcp-activedirectory

search_users

Find users in Active Directory or Azure AD by name, email, department, job title, or phone number using partial match queries.

Instructions

Advanced user search by any field: name, email, department, job title, or phone number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSearch by display name or CN (partial match)
emailNoSearch by email address (partial match)
departmentNoSearch by department (partial match)
titleNoSearch by job title (partial match)
phoneNoSearch by telephone number (partial match)
upnNoSearch by User Principal Name (partial match)
max_resultsNoMaximum number of results
sourceNoData source: "ad" for on-prem LDAP, "azure" for Azure AD/Entra ID (available: ad, azure)ad
Behavior2/5

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

With no annotations, description carries full burden. Only states it's an 'advanced search' but omits behavioral details like result format, pagination, or side effects. Partial match behavior is only in schema, not description.

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?

Single sentence that is front-loaded with key action and resource. No unnecessary words, perfectly concise for a straightforward search tool.

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?

Despite 8 parameters and no output schema, description fails to explain return values, sorting, pagination, or other search behavior. Incomplete for an advanced search 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 coverage is 100% with detailed parameter descriptions. Description adds value by listing fields in context but does not significantly enhance understanding beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly specifies the verb 'search' and resource 'users', lists multiple searchable fields (name, email, etc.), and distinguishes from siblings like 'list_users' and 'get_user' by emphasizing advanced search capabilities.

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 on when to use this tool versus alternatives such as 'get_user' for exact match or 'list_users' for listing. Does not mention when not to use or any prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredriksknese/mcp-activedirectory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server