Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_sleuthkit_fls

Destructive

Run Sleuth Kit fls to list files and directories in forensic disk images, with direct argv execution inside an engagement workspace for artifact analysis.

Instructions

Run sleuthkit fls from the OpenCyber forensics toolkit. The container executes fls directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_sleuthkit_fls"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

The definition adds genuinely useful execution context beyond the annotations: argv tokens are passed directly with no shell parsing, and the process runs inside the selected engagement namespace with relative paths. However, annotations declare destructiveHint=true while the description gives no hint of what could be destroyed or how to avoid it, and it says nothing about the stdin channel or working-directory defaults.

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 short sentences, each front-loaded with the important fact (what runs, how it executes, where it executes) and no filler or repetition.

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?

For a forensic tool taking a free-form argv array with zero schema documentation and a destructive annotation, the definition leaves too much open: the semantics of fls, the argv vocabulary, and the stdin/working-directory behavior. Although an output schema exists and need not be re-explained, the input side remains under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry all parameter meaning, and it largely does not. It obliquely covers 'arguments' ('supplied argv tokens') and hints at 'working_directory' via relative paths, but it never documents the argv format/flags, and 'stdin' is not mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action as 'Run sleuthkit fls from the OpenCyber forensics toolkit', which identifies the exact binary but never explains what fls actually does (list file/directory entries in a disk image). An agent unfamiliar with Sleuth Kit cannot distinguish this from the sibling oc_sleuthkit_icat, which likewise operates on an engagement filesystem but extracts file content.

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

Usage Guidelines2/5

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

The only guidance is 'use relative paths for engagement artifacts', which is a path convention, not a when-to-use rule. There is no statement of when fls is preferred over icat or binwalk, what precondition (a filesystem image in the engagement) must hold, or when not to call it.

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