@intangle/mcp-server 2.6.20 → 2.6.22

package/dist/tool-definitions.js

@@ -122,8 +122,10 @@ const BASE_TOOLS = [
                         "relevance",
                         "recent",
                         "oldest",
-                        "priority"
-                    ]
+                        "priority",
+                        "updated"
+                    ],
+                    description: "Defaults to relevance, or recent when mode is recent. recent and oldest order by each result's stored timestamp (creation time for most Items); updated orders by updated_at, newest first, and falls back to the stored timestamp when an Item has no updated_at."
                 },
                 include: {
                     type: "string",
@@ -138,14 +140,14 @@ const BASE_TOOLS = [
                 limit: {
                     type: "integer",
                     minimum: 1,
-                    maximum: 100,
-                    default: 20
+                    maximum: 500,
+                    description: "Matches per page, at most 500. Set it to what the question needs, for example 3 for the three most recent. Omitted, a page holds 200 matches (25 for semantic search). A page also stops early at the token budget; has_more and next_offset continue it, and there is no cap on the total number of matches."
                 },
                 offset: {
                     type: "integer",
                     minimum: 0,
-                    maximum: 10000,
-                    default: 0
+                    default: 0,
+                    description: "Pass the previous page's next_offset to continue."
                 }
             },
             required: []
@@ -184,11 +186,10 @@ const BASE_TOOLS = [
                 ids: {
                     type: "array",
                     minItems: 1,
-                    maxItems: 500,
                     items: {
                         type: "string"
                     },
-                    description: "Exact canonical or legacy Item IDs, returned in requested order."
+                    description: "Exact canonical or legacy Item IDs, returned in requested order. Any number may be requested; they are read one page at a time."
                 },
                 under: {
                     type: "string",
@@ -203,14 +204,14 @@ const BASE_TOOLS = [
                 limit: {
                     type: "integer",
                     minimum: 1,
-                    maximum: 200,
-                    default: 50,
-                    description: "Maximum Items in this page."
+                    maximum: 500,
+                    default: 200,
+                    description: "Items per page, at most 500; defaults to 200. A page also stops early at the token budget. has_more and next_offset continue it; there is no cap on the total number of Items."
                 },
                 offset: {
                     type: "integer",
                     minimum: 0,
-                    description: "Items to skip in stable breadth-first order. items mode supports up to 5000; structure has no offset cap."
+                    description: "Items to skip in stable breadth-first order. Pass the previous page's next_offset to continue. Neither mode has an offset cap."
                 },
                 include: {
                     type: "array",
@@ -824,7 +825,7 @@ const BASE_TOOLS = [
     {
         name: "message",
         title: "Message Assistant",
-        description: "Primary way to use Intangle for memory, communicating and collaborating with Tan agent in a shared thread. Send a request and either wait for one assistant turn to complete or submit asynchronously for later polling. Intangle derives the durable participant identity from the authenticated runner rather than caller-supplied fields. Conversations are backed by `summary_*` IDs; reuse the returned `conversation_id` and reuse the returned `session_id` so callers can continue the same thread reliably across turns. For shared Item coordination, pass the stable Item Room identity as `channel_id` using `item|<item_id>`; this Item room/channel coordinate is preferred. `project_id`, `group_id`, and legacy `project|...` or `group|...` channel values remain accepted only as compatibility coordinates for older stored calls and integrations. The stable idempotency key anchors retries to one durable turn, and the returned `conversation_id` remains the durable thread anchor.",
+        description: "Primary way to use Intangle for memory, communicating and collaborating with Tan agent in a shared thread. Send a request and either wait for one assistant turn to complete or submit asynchronously for later polling. Intangle derives the durable participant identity from the authenticated runner rather than caller-supplied fields. Conversations are backed by `summary_*` IDs; reuse the returned `conversation_id` and reuse the returned `session_id` so callers can continue the same thread reliably across turns. For shared Item coordination, pass the stable Item Room identity as `channel_id` using `item|<item_id>`; this Item room/channel coordinate is preferred. `project_id`, `group_id`, and legacy `project|...` or `group|...` channel values remain accepted only as compatibility coordinates for older stored calls and integrations. The stable idempotency key anchors retries to one durable turn, and the returned `conversation_id` remains the durable thread anchor. Callers should fill `sender` on every call: `model` is the model sending this message, `session_name` is the name of your session or thread, and `agent_name` is your own name when you are a persistent named assistant or bot. Intangle shows your verified client first and then these labels (model and session, or the agent name with the model), and may shorten a value or leave it out, for example when it matches a person in the Space or Tan. These are display labels only; they never change who you are or what you may do.",
         inputSchema: {
             type: "object",
             properties: {
@@ -888,6 +889,25 @@ const BASE_TOOLS = [
                 timezone: {
                     type: "string",
                     description: "Optional IANA timezone for assistant context."
+                },
+                sender: {
+                    type: "object",
+                    description: "Display labels for who is sending this message. Fill it on every call. Display only: it never changes your verified identity or permissions, and a value may be shortened or left out.",
+                    properties: {
+                        model: {
+                            type: "string",
+                            description: "The model sending this message right now, as a person would say it, for example `Claude Opus 5.5` or `GPT-5.5`. Stored with the message, so a later model change does not rewrite it."
+                        },
+                        session_name: {
+                            type: "string",
+                            description: "The name of your session or thread, for example the title you or the user gave it. Shown next to the model."
+                        },
+                        agent_name: {
+                            type: "string",
+                            description: "Only if you are a persistent named assistant or bot with its own identity: that name. It is shown instead of the session name."
+                        }
+                    },
+                    additionalProperties: false
                 }
             },
             required: [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intangle/mcp-server",
-  "version": "2.6.20",
+  "version": "2.6.22",
   "description": "Model Context Protocol server for Intangle - AI context that persists across conversations",
   "main": "dist/index.js",
   "type": "module",
@@ -56,5 +56,5 @@
     "tsx": "^4.0.0",
     "typescript": "^5.0.0"
   },
-  "intangleSourceHash": "8cbc22fac71d3139119b38680db7337458c57e1a36d23033969618c3b8458dcb"
+  "intangleSourceHash": "9dea3964a786eb78e3e4041fe3d4f1dbe7317c72b06cd6d3a25b8ae89505d224"
 }