Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

investigate_user_activity

Correlates browser history, ShellBags, LNK files, and RecentDocs to reveal what a user browsed, accessed, and navigated. Provides a complete picture of user activity for forensic analysis.

Instructions

Comprehensive user activity investigation. Correlates Browser History, ShellBags, LNK files, and RecentDocs to build a complete picture of user activity. Answers: What did the user browse? What files did they access? What folders did they navigate?

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results per source
keywordNoOptional keyword to search across all sources (URLs, filenames, paths)
lnk_pathNoOverride auto-detected Recent LNK folder path
usernameNoOptional username to narrow artifact search in multi-user images
ntuser_pathNoOverride auto-detected NTUSER.DAT path
browser_pathNoOverride auto-detected browser History path
artifacts_dirYesBase directory containing forensic artifacts or user profile
usrclass_pathNoOverride auto-detected UsrClass.dat path
time_range_endNoISO format datetime - filter events before this time
suspicious_onlyNoFor ShellBags, only return suspicious folder access (temp, AppData, network shares)
time_range_startNoISO format datetime - filter events after this time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses that it correlates multiple sources and can override auto-detected paths, but lacks behavioral context such as whether artifacts must be present, performance impacts, or destructive actions. With no annotations, more detail would be beneficial.

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 concise (three sentences) and front-loaded with the main purpose, followed by sources and questions. No unnecessary words.

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 11 parameters and no output schema, the description does not explain the output format, how correlation results are presented, or potential limitations. This leaves agents without full context for invoking the tool.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning to parameters beyond what the schema already provides, only summarizing the overall purpose.

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 identifies the tool as a comprehensive investigation correlating multiple artifact types (Browser History, ShellBags, LNK files, RecentDocs) to answer specific questions about user activity. It distinguishes itself from sibling tools like browser_get_history or user_parse_shellbags by combining them.

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?

The description implies that this tool is for comprehensive investigation, while siblings cover individual sources. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites.

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