neuro-vault-mcp 5.5.0 → 5.5.3

package/dist/cli.js

@@ -16330,9 +16330,10 @@ var ObsidianCLIProvider = class {
     );
   }
   buildArgs(command, ...kvPairs) {
-    const args = [command, ...kvPairs];
-    if (this.vaultName) args.push(`vault=${this.vaultName}`);
-    return args;
+    if (this.vaultName) {
+      return [`vault=${this.vaultName}`, command, ...kvPairs];
+    }
+    return [command, ...kvPairs];
   }
 };
 
@@ -17066,7 +17067,7 @@ This vault is the user's personal knowledge base \u2014 planning notes, brainsto
 
 You don't know on your own how the user scopes notes for the current project \u2014 the same vault is typically connected to many, and different users organise differently (a tag, a folder, a frontmatter property like \`project\`, or a combination). The user's project-level instructions should name that scope and tell you how to query for it. If they don't, you have three ways forward, in order of preference:
 
-1. **Probe the vault structure** via \`list_tags\`, \`list_properties\`, and exploratory \`query_notes\` calls \u2014 common conventions (a \`project\` frontmatter field, a \`Projects/\` folder, a recurring tag) usually surface immediately and tell you how this vault is organised.
+1. **Probe the vault structure** via \`get_vault_overview\` \u2014 a single-call snapshot of top-level folders with counts, top tags, frontmatter properties with inferred types, and the top-linked notes. Common conventions (a \`project\` frontmatter field, a \`Projects/\` folder, a recurring tag) usually surface immediately. Fall back to \`list_tags\`, \`list_properties\`, or exploratory \`query_notes\` only when the overview misses what you need.
 2. **Use \`search_notes\`** with the project name and key concepts as a fuzzy entry point \u2014 relevant material may exist under unrelated names.
 3. **Ask the user**, and the first time they save project-specific notes propose a scoping scheme so future sessions have an explicit entry point.