@ziggs-ai/ziggs-mcp 0.30.0 → 0.30.1

package/dist/toolAliases.d.ts

@@ -5,8 +5,8 @@
  * tool, and it matched on name and title only. That is fine when the caller
  * already speaks our vocabulary and useless when it does not: searching "hire"
  * returned `ziggs_agreement_handoff` — one tool, and the wrong one — because
- * "hire" happened to appear in that title and nowhere else. The right answer,
- * `ziggs_agreement_buy`, has neither the word in its name nor in its title.
+ * "hire" happened to appear in that title and nowhere else. The default door
+ * is `ziggs_agreement_claim`; `ziggs_agreement_buy` is the direct proposal.
  *
  * So a tool may declare the words a caller is likely to reach for. Aliases are
  * a DISCOVERY aid and nothing else: they never become callable names, never
@@ -16,7 +16,8 @@
  * Two kinds of word belong here:
  *
  * 1. The plain-English word for the intent, when our name is a term of art.
- *    "hire" for buy, "subcontract" for the parent-rail verb.
+ *    "hire" for claim (the default) and for buy (a direct proposal),
+ *    "subcontract" for the parent-rail verb.
  * 2. A name we retired. `agreement_commission` and `agreement_quest` were
  *    renamed before the surface went public; anything still holding the old
  *    word searches it and lands on the tool that replaced it, rather than on

package/dist/toolAliases.js

@@ -5,8 +5,8 @@
  * tool, and it matched on name and title only. That is fine when the caller
  * already speaks our vocabulary and useless when it does not: searching "hire"
  * returned `ziggs_agreement_handoff` — one tool, and the wrong one — because
- * "hire" happened to appear in that title and nowhere else. The right answer,
- * `ziggs_agreement_buy`, has neither the word in its name nor in its title.
+ * "hire" happened to appear in that title and nowhere else. The default door
+ * is `ziggs_agreement_claim`; `ziggs_agreement_buy` is the direct proposal.
  *
  * So a tool may declare the words a caller is likely to reach for. Aliases are
  * a DISCOVERY aid and nothing else: they never become callable names, never
@@ -16,17 +16,31 @@
  * Two kinds of word belong here:
  *
  * 1. The plain-English word for the intent, when our name is a term of art.
- *    "hire" for buy, "subcontract" for the parent-rail verb.
+ *    "hire" for claim (the default) and for buy (a direct proposal),
+ *    "subcontract" for the parent-rail verb.
  * 2. A name we retired. `agreement_commission` and `agreement_quest` were
  *    renamed before the surface went public; anything still holding the old
  *    word searches it and lands on the tool that replaced it, rather than on
  *    nothing.
  */
 export const SEARCH_ALIASES = {
-    ziggs_chat_open: ['contact', 'teammate', 'colleague', 'start conversation', 'create chat', 'message someone'],
+    ziggs_chat_open: [
+        'contact',
+        'teammate',
+        'colleague',
+        'start conversation',
+        'create chat',
+        'message someone',
+        'room',
+        'group',
+        'channel',
+        'invite',
+        'add people',
+    ],
     ziggs_agent_search: ['teammate', 'colleague', 'directory', 'find person'],
     ziggs_access_request: ['access', 'permission', 'request access', 'chat', 'approval', 'grant'],
     ziggs_context_request: ['grant', 'permission', 'restricted', 'request access', 'unlock document'],
+    ziggs_agreement_claim: ['hire'],
     ziggs_agreement_buy: [
         'hire',
         'commission', // retired name

package/dist/tools.js

@@ -762,7 +762,7 @@ export function registerZiggsTools(server, creds, cfg) {
      * had to keep: an assistant polling while its person waits cannot be stopped
      * for a permission prompt on every poll.
      */
-    registerStrictTool(server, 'ziggs_inbox_ack', 'Hand back what you have handled. Reading never clears anything; the watermark moves only here. Acking asserts you handled these ASSIGNED rows: the resourceIds you pass (assigneeId = you; request agreementIds too). Reads of rows assigned to others never count; skip them freely. Pass an `ackTo` back VERBATIM (it is opaque; the per-mailbox watermarks ride inside): the envelope\'s to hand back the whole window, or a delivery row\'s own `ackTo` to stop early, listing the assigned ids up to and including that row; the rest stays for the next pass. An older `ack` is a no-op, so a repeat is safe. The last step of a readPlan is this call, pre-filled.', {
+    registerStrictTool(server, 'ziggs_inbox_ack', 'Hand back what you have handled. Reading never clears anything; the watermark moves only here. Acking asserts you handled these ASSIGNED rows: the resourceIds you pass (assigneeId = you; request agreementIds too). Reads of rows assigned to others never count; skip them freely. Pass an `ackTo` back VERBATIM (it is opaque; the per-mailbox watermarks ride inside): the envelope\'s to hand back the whole window, or a delivery row\'s own `ackTo` to stop early, listing the assigned ids up to and including that row; the rest stays for the next pass. An older `ack` is a no-op, so a repeat is safe. The server refuses an ack that would bury a delivery assigned to you (INBOX_ACK_UNHANDLED). An empty handledResourceIds is safe when nothing in the window is assigned to you. The last step of a readPlan is this call, pre-filled.', {
         ack: z
             .string()
             .describe("An `ackTo` from a previous ziggs_inbox call, passed back VERBATIM: the envelope's for the whole window, or a delivery row's own to stop early at that row. Opaque and monotonic (an older value is a no-op)."),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ziggs-ai/ziggs-mcp",
-  "version": "0.30.0",
+  "version": "0.30.1",
   "description": "MCP server for Claude Code, Cursor, and other MCP hosts — act as your Ziggs delegate agent",
   "type": "module",
   "bin": {
@@ -39,7 +39,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@ziggs-ai/api-client": "0.30.0",
+    "@ziggs-ai/api-client": "0.30.1",
     "dotenv": "^16.6.1",
     "zod": "^3.24.2",
     "zod-to-json-schema": "^3.25.1"