Skip to main content
Glama
MCP Active Directory Server

MCP Active Directory Server

by AlexLiAtDuo

ad_get_security_events

Query recent Windows authentication events (4624, 4625, 4768, 4769, 4776) from a domain controller to investigate logons, failures, and Kerberos activity; filter by user, time, or event ID.

Instructions

Get recent Windows Security events related to authentication (4624, 4625, 4768, 4769, 4776)

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

Input Schema

NameRequiredDescriptionDefault
targetNoTarget DC to run against (e.g., "DC1", "DC2"). Omit to use default.
minutesNoHow many minutes back to search (default: 5, max: 1440)
eventIdsNoSpecific event IDs to filter. Default: [4624, 4625, 4768, 4769, 4776]
usernameNoFilter by username (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the read-shaped verb "Get". It does not state permission requirements for reading the Security log, whether it contacts a remote DC synchronously, latency or failure behavior, or what the response looks like.

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?

A single front-loaded sentence with no filler, and the event ID enumeration is the key discriminator. It is arguably under-specified rather than padded, but nothing is wasted.

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 four-parameter query tool with no annotations and no output schema, the description covers what is queried but not the return shape or operational constraints. The rich schema compensates for the parameter side, leaving behavioral gaps.

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 target, minutes, eventIds, and username are already fully documented including defaults and the 1440-minute cap. The description only repeats the default event ID set, adding no meaning beyond the schema.

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?

Names a specific verb and resource ("Get recent Windows Security events") plus the authentication scope and the concrete event IDs covered. An agent can tell this is an auth-event query, though the description never positions it against siblings like ad_ldap_query or ad_test_kerberos_auth.

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?

Usage is only implied by the phrase "related to authentication" and the event ID list, which tells an experienced agent this is for logon/Kerberos auditing. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling for broader event or LDAP queries.

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