Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_diagnose_winrm

Diagnose WinRM configuration on a target domain controller, including listeners, firewall rules, network profile, and service status, to troubleshoot connectivity issues.

Instructions

Diagnose WinRM configuration on target (listeners, firewall rules, network profile, service status). Use to troubleshoot connectivity issues.

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

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

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the diagnostic scope (what is inspected), which is genuinely useful, but says nothing about whether any configuration is modified, what privileges are required against the target DC, or what the returned report looks like. For an unannotated tool, that leaves real behavioral gaps.

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

Conciseness5/5

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

Two short sentences, with the concrete diagnostic scope front-loaded before the usage hint. There is no redundant restatement of the tool name and no padding.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter diagnostic tool with no annotations and no output schema, the enumerated checks give an agent a good picture of what is probed. What remains unstated is the permission/credential requirement and the shape of the report returned, which matters somewhat since no output schema documents the result.

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' parameter is fully documented in the schema, including the 'omit to use default' behavior. The description only echoes this with 'on target' and adds no format, naming, or resolution detail beyond the schema, so the baseline of 3 is appropriate.

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 specific verb ('Diagnose') tied to a specific resource ('WinRM configuration') and then enumerates the sub-checks (listeners, firewall rules, network profile, service status), which clearly separates it from the LDAP/Kerberos-oriented siblings. It stops short of naming which sibling to use for adjacent connectivity problems, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use to troubleshoot connectivity issues' implies the scenario but is vague about which connectivity problems belong here versus ad_test_kerberos_auth, ad_test_ldap_bind, or ad_get_dc_info. There are no explicit exclusions, prerequisites, or alternative routing, so the agent must infer the boundary.

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