Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_test_kerberos_auth

Tests Kerberos authentication by requesting a TGT for a user, returning success or failure and ticket details to diagnose Active Directory login issues.

Instructions

Test Kerberos authentication by requesting a TGT for a user. Returns success/failure and ticket info.

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": {
      "username": "<username>",
      "password": "<password>"
    },
    "name": "ad_test_kerberos_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoTarget DC name from credentials (optional)
passwordYesPassword for the user
usernameYesUsername to authenticate (without domain)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 does disclose the return shape (success/failure plus ticket info), but says nothing about how failures surface (exception vs. result object), account-lockout risk from repeated bad passwords, audit logging, or whether a real TGT is left behind on the host. For a credential-handling auth test, that is a meaningful gap.

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 sentences, zero filler, with the action front-loaded and the return value trailing. Every clause earns its place.

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?

No annotations and no output schema, so the description must cover both behavior and results. It gestures at the return value ('success/failure and ticket info') but omits prerequisites, failure modes, and whether the test proves only KDC reachability or full end-to-end authentication — all material for a diagnostic an agent will act on.

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%, so username, password, and optional target are already documented in the schema. The description adds no additional meaning, such as a domain-qualified vs. bare username expectation or how target relates to the DC used for the KDC request. 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?

States a specific verb and resource: 'Test Kerberos authentication by requesting a TGT for a user.' The Kerberos/TGT specificity naturally separates it from an LDAP bind or WinRM diagnostic without needing to name siblings. It stops short of explicitly contrasting alternatives, so a 4 rather than a 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 when-to-use or when-not-to-use guidance. An agent troubleshooting domain auth has no stated basis for choosing this over ad_test_ldap_bind or ad_diagnose_winrm, nor any stated preconditions (domain-joined host, DC reachability) that would make the test meaningful.

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