Skip to main content
Glama
Sign In
Microsoft Active Directory MCP Server

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_list_computers

Lists computers in an Active Directory domain, with optional filters for enabled-only status, search base, and result limit.

Instructions

[Computers & Devices] [READ] Listar computadores do dominio.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
search_baseNo
enabled_onlyNo
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden, and it contributes only the implied read-only tag. It says nothing about pagination behavior despite a limit default of 100, required AD permissions, or what happens when search_base is omitted.

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

Conciseness3/5

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

It is a single front-loaded sentence with zero wasted words, but it is under-specified rather than concise — brevity here costs the agent information rather than saving it effort.

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 explained, but with no annotations and zero parameter coverage the description leaves the agent without the usage and scoping information needed to call this list tool confidently alongside many similar siblings.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description explains none of them — not limit, search_base, enabled_only, or correlation_id. The enabled_only filter in particular is a meaningful selection control that an agent would benefit from seeing described.

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 names a specific verb and resource ("Listar computadores do dominio") and the [READ] tag signals the operation class, so an agent knows it retrieves computer objects. However, it does not distinguish itself from siblings like ad_search_computers or ad_get_computer, which an agent would need in order 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus ad_search_computers (search) or ad_get_computer (fetch one), and no prerequisites or exclusions are mentioned. The agent must infer the distinction from the name alone.

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