Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_get_dc_info

Retrieve basic Domain Controller details such as hostname, OS, uptime, and services to help diagnose Active Directory infrastructure.

Instructions

Get basic info about the Domain Controller (hostname, OS, uptime, services)

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

Input Schema

NameRequiredDescriptionDefault
targetNoTarget DC to run against (e.g., "DC1", "DC2"). Omit to use default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Get basic info' does imply a read-only, non-destructive operation and the parenthetical lists what comes back, which compensates somewhat for the absent output schema. However, it says nothing about required permissions, what happens if the target is unreachable, or output format.

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 short sentence with the resource and returned fields front-loaded and no filler. It is efficient, though the terseness contributes to the missing guidance noted elsewhere.

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?

For a one-optional-parameter read tool the description is broadly adequate, and listing the returned fields partially substitutes for the missing output schema. It omits access prerequisites and failure behavior, which matter for a tool that reaches out to a remote Domain Controller.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'target' property is already documented as the DC to run against with an 'omit to use default' fallback. The description adds no meaning beyond that, so the baseline 3 applies.

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 pairs a specific verb ('Get') with a precise resource ('basic info about the Domain Controller') and enumerates the fields returned (hostname, OS, uptime, services), which clearly separates it from siblings like ad_get_security_events or ad_get_user_groups. It stops short of explicitly naming a contrasting sibling, so it lands at 4 rather than 5.

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 explicit when-to-use guidance, no prerequisites (e.g., WinRM/administrative access), and no mention of alternatives such as ad_diagnose_winrm when the DC is unreachable. The purpose is inferable from the wording, but the agent gets no routing help.

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