Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b

disk_parse_usn_journal

Parse the USN Journal to retrieve file system change history, including file creation, deletion, modification, and rename events for forensic analysis.

Instructions

Parse $UsnJrnl:$J (USN Journal) for file system change history. Records file creation, deletion, modification, and rename operations. Answers: What files were created/deleted/renamed? When did file changes occur?

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usn_pathYesPath to $J file (typically $Extend/$J)
filename_filterNoFilter by filename (case-insensitive substring)
reason_filterNoFilter by reason types (e.g., FILE_CREATE, FILE_DELETE, RENAME_NEW_NAME)
time_range_startNoISO format datetime - filter events after this time
time_range_endNoISO format datetime - filter events before this time
interesting_onlyNoOnly return forensically interesting changes (create, delete, rename, modify)
files_onlyNoOnly return file events (exclude directories)
output_modeNoOutput mode: records (individual changes), summary (statistics), deleted_files (only deletions)records
extension_filterNoFilter by file extension (for deleted_files mode)
limitNoMaximum number of records to return
Behavior3/5

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

No annotations are provided, so the description must stand alone. It implies a read-only operation (parsing), but does not explicitly state non-destructive behavior, required permissions, or any side effects. It adds moderate context about the kind of information returned.

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?

Description is very concise (two sentences, ~40 words), front-loading the purpose and key questions answered. No extraneous information.

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?

With 10 parameters and no annotations or output schema, the description covers the primary purpose but does not explain output modes, filtering nuances, or how parameters interact. Adequate for a simple parse tool but could be more comprehensive.

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?

Input schema has 100% description coverage, with detailed descriptions for each parameter. The tool description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly identifies the tool as parsing the USN Journal for file system change history, with specific operations (create, delete, modify, rename). It distinguishes itself from sibling disk_parse_* tools by the target artifact ($J file).

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 explicit guidance on when to use this tool versus alternatives like disk_parse_mft. The description states what questions it answers but does not compare or contrast with other tools, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x746b/winforensics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server