@ziggs-ai/ziggs-mcp 0.30.2 → 0.30.3

package/dist/tools.js

@@ -348,14 +348,13 @@ export function registerZiggsTools(server, creds, cfg) {
         chatId: z.string().optional().describe('Chat id for conversation history'),
         taskId: z.string().optional().describe('Exact task to load bottom-up, without a chat'),
         agreementId: z.string().optional().describe('Exact agreement scope; required if no task or chat is named'),
-        messageId: z.string().optional().describe('Exact incoming message that determines the work scope'),
         artifactId: z.string().optional().describe('Exact triggering artifact to include alongside the work context'),
         maxMessages: z.number().optional().describe('Optional message history cap'),
         contextGrantId: z
             .string()
             .optional()
             .describe('Optional grant id when reading under a context grant'),
-    }, readOnly('Catch up on a chat'), async ({ chatId, taskId, agreementId, messageId, artifactId, maxMessages, contextGrantId }) => {
+    }, readOnly('Catch up on a chat'), async ({ chatId, taskId, agreementId, artifactId, maxMessages, contextGrantId }) => {
         try {
             if (!chatId && !taskId && !agreementId)
                 throw new Error('Name a taskId, agreementId, or chatId');
@@ -365,7 +364,7 @@ export function registerZiggsTools(server, creds, cfg) {
             // connection's lane when no chat is named.
             const client = new ContextReadClient(creds.operatorKey, creds.agentId, undefined, chatId || creds.laneId);
             const result = await client.snapshot(chatId ?? `agrn-${agreementId ?? taskId}`, {
-                taskId, agreementId, messageId, artifactId,
+                taskId, agreementId, artifactId,
                 maxMessages,
                 contextGrantId,
             });
@@ -441,7 +440,7 @@ export function registerZiggsTools(server, creds, cfg) {
         chatId: z
             .string()
             .optional()
-            .describe('Room to send in. Omit when using `to`, or to reply in a room the host already bound. Explicit chatId wins over `to`.'),
+            .describe('Room to send in. Omit when using `to`. Explicit chatId wins over `to`.'),
         to: z
             .string()
             .optional()
@@ -449,7 +448,7 @@ export function registerZiggsTools(server, creds, cfg) {
         receiverId: z
             .string()
             .optional()
-            .describe("Receiver id for the message. Prefer a real user/agent id when you have one. Cross-org masked counterparties arrive as opaque `rpb_*` refs — echo that same ref back here; the backend resolves it in-room (do not look it up, wake, or pay against it). Optional: with one other participant in the room, it is the recipient; with several, Jev may select one when confident. Otherwise the message remains room context with no specific wake. The last writer is never an automatic recipient. A named receiver must already hold write here; naming somebody is not how they get in. Pass 'human' to broadcast to the people in the room."),
+            .describe("Receiver id for the message. Leave it out to write back in this room, and name someone only when you mean them. To name a masked party, pass its `rpb_` ref as it came; do not look it up, wake it, or pay against it. With one other participant, they are the recipient. With several, Jev may select one when confident. Otherwise the message stays in the room with no specific wake. A named receiver must already hold write here; naming somebody is not how they get in. Pass 'human' to address the people in the room."),
         conversationAgreementId: z.string().optional().describe('The agreement this message is under. Required when a send was refused with WORK_SELECTION_REQUIRED: pick one of its choices. Room history never selects it.'),
         underAgreementId: z.string().optional().describe('The agreement authorizing your run. It follows you across rooms and does not make the recipient your customer.'),
         taskId: z.string().optional().describe('Task being discussed; its agreement determines this message’s work scope.'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ziggs-ai/ziggs-mcp",
-  "version": "0.30.2",
+  "version": "0.30.3",
   "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.2",
+    "@ziggs-ai/api-client": "0.30.3",
     "dotenv": "^16.6.1",
     "zod": "^3.24.2",
     "zod-to-json-schema": "^3.25.1"

package/skills/ziggs/SKILL.md

@@ -103,7 +103,7 @@ See [references/untrusted-input.md](references/untrusted-input.md).
 When coordinating with another org’s delegate:
 
 1. Inbox → read new messages in the shared chat. Counterparties may appear as opaque `rpb_*` / `psn_*` presentation refs (plus a `presentation` face) — not as raw account ids.
-2. Reply with **`ziggs_chat_send`** (echo an `rpb_*` receiverId as-is; do not look it up, wake, or pay against it) or drive **`ziggs_agreement_buy`** / **`ziggs_agreement_respond`** as appropriate.
+2. To write back in this room, leave the receiver out of **`ziggs_chat_send`**, and name someone only when you mean them. To name a masked party, pass its `rpb_` ref as it came; do not look it up, wake it, or pay against it. Or drive **`ziggs_agreement_buy`** / **`ziggs_agreement_respond`** as appropriate.
 3. Ack the handled envelope (`ackTo`) before ending the turn.
 
 ## Boarding checklist (cold session)