Find EVTX (Windows Event Log) files in a specified directory. Use recursive search to locate logs across subfolders, enabling quick identification of forensic artifacts for further analysis.
List all EVTX (Windows Event Log) files in a directory.
| Name | Required | Description | Default |
|---|---|---|---|
| directory | Yes | Directory path to search | |
| recursive | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; the description only says 'list files' without disclosing error handling, file filtering behavior, or performance implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, concise but too brief to provide necessary details; it's not overlong but lacks substance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no annotations, and only partial param descriptions, the description should explain return format, sorting, or filtering; it does not.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50% (only 'directory' has description); the tool description adds no extra meaning beyond what's in the schema, failing to compensate for the missing 'recursive' description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (list) and resource (EVTX files in a directory), and it distinguishes from siblings like evtx_search and evtx_attack_summary by specifying file listing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., evtx_search), no when-not-to-use conditions, and no prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.