@intangle/mcp-server 2.6.28 → 2.6.30

package/dist/highq-tool-definitions.js

@@ -282,7 +282,7 @@ export const HIGHQ_DIRECT_TOOLS = [
     {
         name: "HIGHQ_GET_FILE_CONTENT",
         title: "Get HighQ File Content",
-        description: "Retrieve text when safely extractable from one HighQ file, otherwise return metadata and a retrieval hint. Raw binary payloads are not returned.",
+        description: "Retrieve one HighQ document library file. Pass original=true for original bytes in content_base64, with filename, content_type and content_length, without text extraction. Otherwise return extracted text when available or a retrieval hint. Request attachments use the File Item handles from HIGHQ_GET_LEGAL_REVIEW_CONTEXT.",
         inputSchema: {
             type: "object",
             properties: {
@@ -304,7 +304,7 @@ export const HIGHQ_DIRECT_TOOLS = [
                 },
                 original: {
                     type: "boolean",
-                    description: "Optional request for the original file on older HighQ APIs."
+                    description: "Set true to retrieve original base64 bytes without text extraction. Decode content_base64 and check content_length before opening the file."
                 },
                 get_converted_file: {
                     type: "boolean",

package/dist/tool-definitions.js

@@ -248,7 +248,7 @@ const BASE_TOOLS = [
     {
         name: "update_items",
         title: "Update Items",
-        description: "Apply an ordered batch of create, update, move, or delete Item operations through Phoenix authority. Every Item is a Room. Results preserve operation order and report partial failures explicitly.",
+        description: "Apply an ordered batch of create, update, move, or delete Item operations through Phoenix authority. Every Item is a Room. Results preserve operation order and report partial failures explicitly. Keep Item content short and plain: key result first, detail only when needed, no walls of text.",
         inputSchema: {
             type: "object",
             additionalProperties: false,
@@ -836,7 +836,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. 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. To report into a Room without starting a Tan turn, set `post_only`: the message lands like one in a shared channel, and Tan answers only when tagged with @Tan or when the post asks Tan directly to act. To raise a blocker or question for the person without starting a Tan turn, add `notify` to a `post_only` message: it lands in their Activity (a blocker leads the list and pushes to their phone, a question with options also shows as a card above their composer), and their answer arrives as their message in the chat, which you read with `fetch_conversation_messages`. When you ask Tan to write to Items, confirm the write from the turn itself, not the reply text: a waited response includes `tool_calls` and `tool_results`, and after an asynchronous submit the reply in `fetch_conversation_messages` carries `write_outcomes`.",
+        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. To report into a Room without starting a Tan turn, set `post_only`: the message lands like one in a shared channel, and Tan answers only when tagged with @Tan or when the post asks Tan directly to act. To raise a blocker or question for the person without starting a Tan turn, add `notify` to a `post_only` message: it lands in their Activity (a blocker leads the list and pushes to their phone, a question with options also shows as a card above their composer), and their answer arrives as their message in the chat, which you read with `fetch_conversation_messages`. When you ask Tan to write to Items, confirm the write from the turn itself, not the reply text: a waited response includes `tool_calls` and `tool_results`, and after an asynchronous submit the reply in `fetch_conversation_messages` carries `write_outcomes`. Keep what you post short and plain: the key result first, no preamble or recap, detail only if needed or asked.",
         inputSchema: {
             type: "object",
             properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intangle/mcp-server",
-  "version": "2.6.28",
+  "version": "2.6.30",
   "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": "fa17c63d2d81795b99e2c84c09dc509487ad64791d98d27c2bebcfcb8ec13eda"
+  "intangleSourceHash": "58b08d74e4507d5bce4917daa3dc8cc126275f1f88911089995ff8dc8890d309"
 }