Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b

hunt_ioc_pack

Hunt behavioral indicators of compromise across exported logs, text artifacts, filenames, and PCAP payloads using a bundled IoC pack.

Instructions

Hunt behavioral IoCs from a metadata pack across exported logs, text artifacts, filenames, and PCAP payloads. Bundled pack: impacket-iocs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artifacts_dirYesBase directory containing forensic artifacts, exported logs, PCAPs, or parsed tool output
packNoBundled pack id/name to loadimpacket-iocs
pack_pathNoOptional external pack directory or pack.json path
scan_filesNoScan plaintext exports/logs and filenames
scan_pcapNoScan PCAP payloads when scapy is installed
max_filesNoMaximum files to inspect
max_file_sizeNoSkip files larger than this many bytes
limitNoMaximum findings/hits to return
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It indicates scanning of various data sources but does not mention side effects, authorization needs, or whether the operation is read-only. Critical behavioral context is missing.

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 exceptionally concise: two sentences front-load the core purpose and a key example. Every word adds value with no redundancy.

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 the tool's complexity (8 parameters) and no output schema, the description covers the main purpose and sources adequately. However, it lacks guidance on workflow, prerequisites, or return format, leaving minor gaps.

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% with each parameter described. The description adds the bundled pack name as an example, but does not significantly augment meaning beyond the schema. 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 verb 'Hunt', the resource 'behavioral IoCs from a metadata pack', and the scope across multiple artifact types (logs, texts, filenames, PCAPs). It distinguishes from sibling 'hunt_ioc' by specifying the bundled pack mechanism.

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 pack-based hunting but does not explicitly state when to use this tool versus alternatives (e.g., hunt_ioc) or when not to use it. 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