@edda-business/mcp 0.68.0 → 0.69.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@edda-business/mcp",
-  "version": "0.68.0",
+  "version": "0.69.0",
   "description": "Edda — the company data layer for AI agents.",
   "license": "Apache-2.0",
   "publishConfig": {

package/src/server.js

@@ -315,12 +315,11 @@ export function createServer() {
   // ===========================================================================
   server.tool(
     "reconcile",
-    "PROCESS the company Inbox. Two modes. (1) Sweep: no arguments — the company auto-files items " +
-    "with a clear destination and leaves ambiguous ones waiting. (2) ANALYZED FILING — the ingest " +
-    "flow: list waiting items with `inbox`, read and analyze each one, then call this with that " +
-    "item's `stagingId` AND an explicit `path` (e.g. 'Projects/Whitehay AI/Working Documents') to " +
-    "file it exactly there. YOU are the analyst; the company only files what you tell it. " +
-    "Returns where each item landed.",
+    "FILE items from the company Inbox — NOTHING files without an explicit per-item action " +
+    "(company ruling). Without arguments this only REPORTS what is waiting (each with a proposed " +
+    "destination). The ingest flow: list items with `inbox`, read and analyze each, then call this " +
+    "with that item's `stagingId` — plus an explicit `path` to place it exactly where you decided " +
+    "(omit `path` to accept the proposed destination). YOU are the analyst; your call is the review.",
     {
       stagingId: z.string().optional().describe("Id of one staged item to file (from an `inbox` row or a submit receipt). Omit to sweep the whole Inbox."),
       path: z.string().optional().describe("Explicit destination folder path for THAT item (requires stagingId). Missing folders are created."),