Microsoft Active Directory MCP Server

Overview Schema Source Related Servers Discussions Admin

ad_create_dns_record

Creates a DNS record in Active Directory to map a name to an IPv4 address or CNAME alias, with optional dry-run validation before committing the change.

Instructions

[DNS & Infrastructure] [WRITE] Criar registro DNS no AD.

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": "<name>"
    },
    "name": "ad_create_dns_record"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`dry_run`	No
`zone_name`	Yes
`cname_alias`	No
`record_type`	No	A
`ttl_seconds`	No
`ipv4_address`	No
`correlation_id`	No
`confirmation_token`	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?

With no annotations, the description carries the full burden and only discloses that this is a write. It says nothing about the dry_run parameter, the confirmation_token (which strongly implies a two-step confirm flow), whether creation is idempotent, or what happens on duplicate records — all critical for a mutation tool.

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 with bracketed category and [WRITE] tags is front-loaded and waste-free, but it is under-specified rather than concise — the brevity comes at the cost of information the agent needs.

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 for a 9-parameter mutation with no annotations and no parameter descriptions the definition is far too thin. The confirmation-token workflow and dry-run semantics in particular are left completely unexplained.

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 description coverage is 0% across 9 parameters, and the description compensates for none of it. The meaning of record_type, cname_alias vs ipv4_address, ttl_seconds, dry_run, correlation_id and confirmation_token is entirely undocumented.

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 states a specific verb and resource ("Criar registro DNS" = create DNS record) plus a category tag and an explicit [WRITE] marker. This distinguishes it from ad_update_dns_record, ad_delete_dns_record and ad_get_dns_record, though it does not clarify supported record types (A vs CNAME) that the schema implies.

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_update_dns_record (existing record) or ad_create_computer, and no mention of prerequisites such as the zone existing or permissions on the DNS zone. The agent must infer all of this from the tool name alone.

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

Deploy Server