Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_test_ldap_bind

Test LDAP simple bind authentication with a username and password to verify Active Directory credentials and return success or failure, with optional LDAPS.

Instructions

Test LDAP simple bind authentication. Returns success/failure.

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

Input Schema

NameRequiredDescriptionDefault
targetNoTarget DC name from credentials (optional)
passwordYesPassword
useLdapsNoUse LDAPS (port 636) instead of LDAP (port 389). Default: false
usernameYesUsername (UPN format: user@domain, or DOMAIN\user)

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 provided, so the description carries the full burden. It states the operation and that it returns success/failure, but omits critical behavior for an authentication test: potential account lockout, plaintext transmission when useLdaps is false, permission requirements, and whether failure responses include diagnostic detail.

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 zero waste, front-loading the operation and then the return value. Nothing is redundant or buried.

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?

Given the tool tests authentication with no annotations and no output schema, the description is too sparse. It should warn about lockout risk, clarify how LDAPS affects credential safety, and describe what failure output contains beyond a bare success/failure indication.

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 all four parameters are already documented in the input schema, including username format and LDAPS behavior. The description adds no parameter-level meaning beyond that baseline.

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: "Test LDAP simple bind authentication." This clearly distinguishes it from the Kerberos authentication sibling, though it does not explicitly name alternatives or scope beyond the protocol.

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?

It implies the tool is for validating LDAP simple bind credentials but gives no guidance on when to choose it over ad_test_kerberos_auth or other diagnostic tools, and no prerequisites or exclusions are stated.

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