Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

evtx_search

Search Windows EVTX log files for events by time range, Event ID, keywords, and provider, with pagination for large result sets.

Instructions

Search events from EVTX file. Filter by time, Event ID, keywords, provider. Supports pagination with offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 50)
offsetNoSkip first N matches for pagination
containsNo
end_timeNo
providerNo
event_idsNo
evtx_pathYes
start_timeNoISO format datetime
not_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • changedInput schema / properties / limit / default
      Previous value: -100New value: +40
    • addedInput schema / properties / limit / description
      Added value: +"Max results to return (default 50)"
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip first N matches for pagination",
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states basic search and filter capabilities and pagination, but omits details like file size handling, error behavior, or permission requirements. This is insufficient for a complex tool.

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, front-loaded with action and resource. Every word carries information: search action, EVTX file, filter capabilities, pagination support. No unnecessary text.

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 9 parameters, low schema coverage, no annotations, and no output schema, the description is incomplete. It fails to explain output format, compound filter logic (AND/OR), or pagination details beyond offset. A more comprehensive description is needed for this complex tool.

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

Parameters2/5

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

Schema coverage is 33% (only 3 of 9 parameters have descriptions). The description mentions filtering by time, Event ID, keywords, provider, but does not clearly map these to specific parameters (e.g., 'keywords' likely maps to 'contains' but not explicit). It adds minimal value beyond the schema for undocumented parameters.

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 clearly states it searches events from an EVTX file and lists filter options (time, Event ID, keywords, provider) and pagination. It differentiates from specialized sibling tools like evtx_attack_summary or evtx_security_search, though it could be more specific about the nature of events returned.

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?

No guidance on when to use this tool versus alternatives such as evtx_security_search or evtx_explain_event_id. It does not mention prerequisites or exclusions, leaving the agent without context for selecting this tool over siblings.

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

Deploy Server

Other Tools