Skip to main content
Glama
Microsoft Active Directory MCP Server

Microsoft Active Directory MCP Server

by nks1097

ad_generate_domain_health_report

Generate an Active Directory domain health report to assess directory status, surface issues, and support diagnostics or compliance reviews.

Instructions

[Reports, Inventory & Automation] [READ] Relatorio de saude 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_generate_domain_health_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_formatNojson
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 behavioral burden; the '[READ]' tag is the only signal that this is a non-mutating operation. It says nothing about scope (whole domain vs. filtered), permissions required, cost/runtime of generating a report, or how it differs from ad_get_directory_health in depth or output.

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 short line with no filler, so nothing is wasted, but it is under-specified rather than concise — there is no front-loaded statement of what the report contains or when it should be produced.

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-format explanation is not required, but for a no-annotation report tool sitting among many overlapping report/health siblings, the definition omits usage boundaries, parameter meaning, and behavioral scope. It is not complete enough for confident selection.

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% for both parameters (output_format, correlation_id), and the description adds no information about either. The parameter names are largely self-explanatory, which prevents a score of 1, but the description does nothing to compensate for the total lack of schema documentation.

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 description translates the tool name into Portuguese ('Relatorio de saude do dominio'), so the resource is identifiable as a domain health report, and the '[Reports, Inventory & Automation] [READ]' prefix signals the category. However, it does not distinguish this from close siblings such as ad_get_directory_health, ad_generate_domain_inventory, or ad_run_compliance_assessment, all of which sound like domain-level health/report operations.

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, what conditions trigger it, or which sibling to prefer instead. With over a dozen report-generation siblings and a dedicated ad_get_directory_health tool, the absence of any routing guidance leaves the agent guessing.

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