Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_compare_directory_snapshots

Compare Active Directory snapshots from different periods to identify added, removed, or changed directory objects and inventory differences.

Instructions

[Reports, Inventory & Automation] [READ] Comparar inventarios de periodos diferentes.

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": {
      "snapshot_a": "<snapshot_a>",
      "snapshot_b": "<snapshot_b>"
    },
    "name": "ad_compare_directory_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
`snapshot_a`	Yes
`snapshot_b`	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

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 burden; the [READ] tag is its only real contribution about behavior. It does not say where snapshot_a/snapshot_b come from, whether comparison is keyed by DN/object, what constitutes a difference, or how large inputs are handled.

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 no filler, so nothing is wasted. The problem is under-specification rather than verbosity, and the tags consume space without adding much beyond category and read-only status.

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 the two open nested-object inputs and the missing snapshot-provenance story leave an agent unable to construct a correct call. For a 3-parameter tool with 0% schema coverage, the description does far too little.

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% and both required parameters are free-form nested objects with additionalProperties=true, so their expected shape is entirely undocumented. The phrase "periodos diferentes" hints that each argument is one period's inventory, but offers no field-level or structural guidance.

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

Purpose3/5

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

The verb+resource is identifiable (compare two inventories from different periods), and the [Reports, Inventory & Automation] / [READ] tags place it in the reporting family. However, it never explains what a "snapshot" is or how it relates to sibling tools like ad_generate_domain_inventory, leaving the object of the comparison vague.

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 versus the many report/inventory generators or ad_compare_gpos, nor any prerequisite such as how snapshots are obtained before comparison. Usage is only inferred from the name and the [READ] tag.

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

Deploy Server