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

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_get_dns_zone

Retrieves DNS zone details and configuration settings to troubleshoot name resolution and verify zone parameters in Active Directory.

Instructions

[DNS & Infrastructure] [READ] Consultar detalhes e configuracoes de zona DNS.

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": {
      "zone_name": "<zone_name>"
    },
    "name": "ad_get_dns_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_nameYes
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, and the only disclosure is the inline [READ] marker implying a non-mutating operation. It says nothing about required permissions, behavior when the zone does not exist, or what "configuracoes" actually encompasses.

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?

A single compact sentence preceded by bracketed category/read tags — front-loaded and free of filler. Its brevity is efficient rather than padded, though the space saved is not spent on useful detail.

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?

The tool is simple (one required param) and an output schema exists, so return values need not be described. Still, for an unannotated read tool that overlaps heavily with ad_list_dns_zones, the description leaves the agent without enough to choose it confidently or know what inputs are valid.

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%, so the description is responsible for compensating and it does not mention either parameter. zone_name is self-evident from its name, but correlation_id (nullable, defaulting to null) is undocumented anywhere and the description offers no help on what zone_name accepts (FQDN vs short name).

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 ("Consultar" / query) and resource ("zona DNS"), plus category tags ([DNS & Infrastructure], [READ]) that immediately frame the tool. It is understandable without opening the schema, but it never distinguishes itself from the close sibling ad_list_dns_zones, which is the main ambiguity an agent would face.

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 guidance on when to use this versus ad_list_dns_zones or ad_get_dns_record, and no prerequisites (e.g., that the zone must exist / be AD-integrated) are stated. The only implicit signal is the word "detalhes", which a caller must interpret on their own.

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