Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b

investigate_user_activity

Identify what users browsed, accessed, and navigated by correlating browser history, ShellBags, LNK files, and RecentDocs.

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

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

With no annotations, the description carries the full burden. It explains that the tool correlates multiple sources but does not disclose read-only status, authentication needs, rate limits, or behavior when artifacts are missing. Lacks detail on return format or any side effects.

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?

Three concise sentences, front-loaded with purpose and key questions. No wasted words.

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 11 parameters and no output schema, the description covers the tool's purpose well. However, it lacks detail on output structure or correlation results. Schema coverage is high, so completeness is largely satisfied.

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 adds no additional meaning beyond what the schema provides. It does not explain relationships between parameters or provide usage tips.

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's purpose: comprehensive user activity investigation correlating multiple artifacts. It explicitly answers specific questions (browsing, file access, folder navigation), distinguishing it from sibling tools that focus on single artifact types.

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 usage for comprehensive investigations but does not explicitly state when to use this tool over alternatives like browser_get_history or user_parse_shellbags. No exclusions or prerequisites are mentioned.

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