Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b

disk_parse_usn_journal

Retrieve file system change history by parsing the USN Journal, uncovering file creation, deletion, modification, and rename operations with precise timestamps.

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 provided, so description must convey behavioral traits. It correctly indicates the tool parses (read-only) a journal file, but lacks details on performance, error handling (e.g., missing $J file), or whether it modifies the source. The description is adequate but not rich in behavioral context.

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?

The description is two concise sentences plus a list of answerable questions. It is front-loaded with core purpose and immediately useful without extra text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters with complete schema descriptions and no output schema, the description adequately covers the tool's purpose and filter capabilities. It does not explain return format, but the output_mode parameter (records/summary/deleted_files) provides sufficient context. Minor gap: no mention of record count or ordering.

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?

With 100% schema description coverage, the input schema already explains each parameter (e.g., usn_path, filename_filter). The tool description adds no further parameter-specific meaning beyond listing filter options in the answer questions. 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?

The description clearly states the tool parses the USN Journal ($UsnJrnl:$J) for file system change history, explicitly listing operations (creation, deletion, modification, rename). This distinguishes it from sibling tools like disk_parse_mft (Master File Table) and disk_parse_prefetch (prefetch files).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies the tool answers when file changes occurred and what files were created/deleted/renamed, implying use for historical file activity. However, it does not explicitly contrast with sibling tools like disk_parse_mft, which serves different forensic purposes, leaving some ambiguity.

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