Skip to main content
Glama
trycatchkamal

Filesystem Watcher MCP

watch_directory

Monitors a directory for file system events like creation, modification, deletion, and moves, returning a watch ID for polling or unwatching.

Instructions

Start watching a directory for file system events.

Returns a watch_id that can be used with poll_events and unwatch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the directory to watch.
recursiveNoIf True, also watch all subdirectories recursively.
extensionsNoOptional list of file extensions to include, e.g. [".py", ".js"]. If omitted, all extensions are reported.
patternNoOptional glob pattern matched against the file *name*, e.g. "*.log". Applied in addition to (not instead of) the extensions filter.
ignore_patternsNoOptional glob patterns to exclude, e.g. ["*.tmp", ".git/*"]. Matched against both the file name and its full path.
event_typesNoOptional subset of event types to report. Valid values: "created", "modified", "deleted", "moved". If omitted, all event types are reported.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries full burden but only states 'start watching' and the return value. No disclosure of side effects, permissions, resource usage, or failure modes (e.g., directory not found).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences), front-loaded with the main action, and avoids repetition. It could include more useful context, but is appropriately sized.

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?

Given the tool's complexity (6 parameters, output schema exists, sibling tools), the description lacks guidance on the watch lifecycle, asynchronous behavior, and how the watch_id integrates with other tools. It is incomplete for a tool that requires follow-up steps.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no extra meaning beyond the schema, earning the baseline score of 3.

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 action ('Start watching a directory') and the resource ('file system events'), and distinguishes itself from sibling tools (list_active_watches, poll_events, unwatch) by initiating the watch.

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 mentions that the returned watch_id is used with poll_events and unwatch, implying the workflow, but does not explicitly state when to use or not use this tool, nor does it provide alternatives or prerequisites.

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/trycatchkamal/filesystemwatcher-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server