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

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_generate_computer_report

Generates a computer inventory report from Active Directory with configurable record limit and output format for auditing and compliance.

Instructions

[Reports, Inventory & Automation] [READ] Gerar relatorio de computadores.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
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 exist, so the description carries the full behavioral burden. The [READ] tag usefully signals a non-mutating operation, but nothing is said about permissions required, the scope of the report, what data it includes, or any limits.

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?

The single sentence is compact and front-loaded with category tags and a READ marker. However, the brevity reflects under-specification rather than disciplined editing.

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?

Although an output schema exists and spares the description from explaining return values, a three-parameter report tool with zero annotations and 0% schema coverage needs far more detail than one sentence about what is generated and how the parameters shape it.

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 coverage is 0% and the description says nothing about the three parameters (limit, output_format, correlation_id). An agent must infer the meaning and accepted values of output_format and correlation_id purely from the names.

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 and resource ('Gerar relatorio de computadores'), which maps cleanly to the tool name. It is clear what the tool produces, but there is no differentiation from siblings such as ad_list_computers or ad_generate_domain_inventory.

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?

The [Reports, Inventory & Automation] category tag hints at the domain, but there is no indication of when to use this versus ad_list_computers, ad_get_stale_computers, or the other report generators. No prerequisites or exclusions are given.

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