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_domain_functional_level

Retrieves the Active Directory domain functional level to verify supported features and compatibility before planning upgrades or configuration changes.

Instructions

[Domain & Domain Controllers] [READ] Consultar nivel funcional 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_get_domain_functional_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 burden; the '[READ]' tag is the only behavioral signal. It does not state required permissions/credentials, whether it contacts a specific DC, latency, or error behavior for unreachable domains.

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 compact sentence with category and access-mode tags front-loaded; nothing is wasted. However, the brevity comes partly from omission rather than tight editing.

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 described, and this is a simple read-only lookup. Still, a caller gets no indication of the domain target, credentials, or how the result differs from forest functional level.

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 parameter correlation_id has 0% schema description coverage and is not mentioned in the description at all. It is likely plumbing, but nothing explains whether it is optional or how it is used.

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 ('Consultar nivel funcional do dominio'), which is more precise than the bare name. The domain-vs-forest scope is implicit in 'do dominio', but the description never names the sibling ad_get_forest_functional_level, leaving the agent to infer the distinction.

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_get_forest_functional_level or ad_get_domain_info, and no prerequisitos or exclusions. Only the bracketed group/READ tag hints at context.

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