neuro-vault-mcp 3.2.1 → 3.3.0

package/dist/cli.js

@@ -15368,10 +15368,18 @@ function normalizePath(raw) {
 var VALID_FIELDS = ["frontmatter", "content"];
 var DEFAULT_FIELDS = ["frontmatter", "content"];
 function validateReadNotesInput(input) {
-  if (!Array.isArray(input.paths)) {
-    throw invalidArgument("paths must be an array", "paths");
+  let paths;
+  if (typeof input.paths === "string") {
+    if (input.paths === "") {
+      throw invalidArgument("paths must not be empty", "paths");
+    }
+    paths = [input.paths];
+  } else if (Array.isArray(input.paths)) {
+    paths = input.paths;
+  } else {
+    throw invalidArgument("paths must be a string or an array of strings", "paths");
   }
-  if (input.paths.length < 1 || input.paths.length > 50) {
+  if (paths.length < 1 || paths.length > 50) {
     throw invalidArgument("paths must contain between 1 and 50 entries", "paths");
   }
   let fields;
@@ -15391,7 +15399,7 @@ function validateReadNotesInput(input) {
     }
     fields = input.fields;
   }
-  return { paths: input.paths, fields };
+  return { paths, fields };
 }
 
 // src/modules/operations/tools/append-daily.ts
@@ -15901,7 +15909,7 @@ function buildReadDailyTool(deps) {
 // src/modules/operations/tools/read-notes.ts
 var readNotesFieldSchema = external_exports.enum(["frontmatter", "content"]);
 var inputSchema12 = external_exports.object({
-  paths: external_exports.array(external_exports.string()).min(1).max(50),
+  paths: external_exports.union([external_exports.string().min(1), external_exports.array(external_exports.string()).min(1).max(50)]),
   fields: external_exports.array(readNotesFieldSchema).min(1).optional()
 });
 function buildReadNotesTool(deps) {
@@ -15909,7 +15917,7 @@ function buildReadNotesTool(deps) {
   return {
     name: "read_notes",
     title: "Read Notes",
-    description: "Read multiple notes in one call. `paths` is an array of 1\u201350 vault-relative POSIX paths; duplicates are de-duplicated and results returned in input order. `fields` projects which parts of each note to return \u2014 choose from `frontmatter` and `content`; default `['frontmatter','content']`. One missing or unreadable path does not fail the others \u2014 per-item errors come back inline. A single MCP roundtrip with parallel disk reads. Reads are direct from disk and do not require Obsidian to be running.",
+    description: "Read one or more notes in one call. `paths` is a vault-relative POSIX path string or an array of 1\u201350 such paths; duplicates are de-duplicated and results returned in input order. `fields` projects which parts of each note to return \u2014 choose from `frontmatter` and `content`; default `['frontmatter','content']`. One missing or unreadable path does not fail the others \u2014 per-item errors come back inline. A single MCP roundtrip with parallel disk reads. Reads are direct from disk and do not require Obsidian to be running.",
     inputSchema: inputSchema12,
     handler: async (input) => {
       const { paths, fields } = validateReadNotesInput(input);
@@ -16084,7 +16092,7 @@ When operating directly inside the vault itself (not from an external project th
 ### Notes (body)
 
 Use \`read_notes\`, \`create_note\`, \`edit_note\`, \`read_daily\`, \`append_daily\` when the user asks to:
-- Read one or more notes by path (\`read_notes\` \u2014 accepts an array of 1\u201350 vault-relative POSIX paths; prefer this over multiple sequential reads)
+- Read one or more notes by path (\`read_notes\` \u2014 accepts a single vault-relative POSIX path string or an array of 1\u201350 such paths; prefer this over multiple sequential reads)
 - Create a new note, task, or idea (\`create_note\`)
 - Add content to an existing note (\`edit_note\`)
 - Read or update today's daily note (\`read_daily\` / \`append_daily\`)
@@ -16136,7 +16144,7 @@ Use \`search_notes\` when the user is recalling a topic fuzzily, asking a concep
 
 ## Routing between operations and semantic
 
-If the user gives an exact anchor (note path, daily note, tag, frontmatter field), prefer operations tools. If the user is recalling fuzzily or asking a conceptual question, prefer \`search_notes\`. After semantic search finds a relevant note, you can read it with \`read_notes\` (passing the path in a one-element array, or batching with sibling paths) to see the details.
+If the user gives an exact anchor (note path, daily note, tag, frontmatter field), prefer operations tools. If the user is recalling fuzzily or asking a conceptual question, prefer \`search_notes\`. After semantic search finds a relevant note, you can read it with \`read_notes\` (passing the path as a single string, or batching with sibling paths in an array) to see the details.
 
 For tag-driven questions ("which notes are tagged X?", "show me everything in #ai") use \`query_notes\` with \`{ filter: { tags: '<name>' } }\`, not \`search_notes\` \u2014 the answer is exact, not fuzzy.
 `;