Fix glab tool context

1 files changed, 19 insertions, 3 deletions

diff --git a/servers/gitlab_glab/README.md b/servers/gitlab_glab/README.md
index 21f40cb..5a6fff1 100644
--- a/servers/gitlab_glab/README.md
+++ b/servers/gitlab_glab/README.md
@@ -50,24 +50,40 @@ Checks if the GitLab CLI tool is installed and accessible.
 result = use_mcp_tool(
     server_name="gitlab_glab",
     tool_name="check_glab_availability",
-    arguments={}
+    arguments={
+        "working_directory": "/path/to/current/directory"
+    }
 )
 ```
 
 ### find_project
 
-Finds a GitLab project by name and returns its ID and other details.
+Finds GitLab projects by name and returns their details.
 
 ```python
 result = use_mcp_tool(
     server_name="gitlab_glab",
     tool_name="find_project",
     arguments={
-        "project_name": "my-project"
+        "project_name": "my-project",
+        "working_directory": "/path/to/current/directory"
     }
 )
 ```
 
+The function returns a list of matching projects, each containing the following fields:
+- `id`: The project ID
+- `name`: The project name
+- `path_with_namespace`: The project path with namespace
+- `web_url`: The project web URL
+- `description`: The project description
+
+## Working Directory Context
+
+All tools require a `working_directory` parameter that specifies the directory context in which the GitLab CLI commands should be executed. This ensures that commands are run in the same directory as the agent, maintaining proper context for repository operations.
+
+The working directory should be the absolute path to the directory where you want the GitLab CLI commands to be executed. For example, if you're working with a GitLab repository cloned to `/home/user/projects/my-repo`, you would pass that path as the `working_directory` parameter.
+
 ## Development
 
 ### Running tests