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_dns_zones

Lists Active Directory-integrated DNS zones to help inspect and audit DNS infrastructure.

Instructions

[DNS & Infrastructure] [READ] Listar zonas DNS integradas ao Active Directory.

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

Input Schema

NameRequiredDescriptionDefault
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, but the [READ] tag does communicate that this is a non-mutating operation. It says nothing about paging, scale of results, or directory permissions required to enumerate zones.

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

Conciseness4/5

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

One front-loaded sentence with no wasted prose, prefixed by category and read-only tags. The tags are boilerplate but aid scanning rather than obscuring the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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. For a simple read-only list tool the description is minimally adequate, but missing permissions context and the undocumented correlation_id leave gaps.

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?

The single correlation_id parameter has 0% schema description coverage and the description adds no meaning for it, leaving its purpose (likely request tracing) undocumented. Impact is limited because it is an optional, generic field.

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 gives a clear verb (list) and resource (DNS zones) plus a scope qualifier (integrated with Active Directory). It does not explicitly name the sibling it complements (ad_get_dns_zone for a single zone), but the list-vs-get distinction is inferable from the neighboring names.

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 ad_get_dns_zone or ad_list_dns_records, and no prerequisites or exclusions. The intended usage (enumerate zones) is only implied by the verb.

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