@bli-cockpit/mcp 0.1.104 → 0.1.105

package/dist/search-tool.d.ts

@@ -1,5 +1,5 @@
 /**
- * `tower_search` — one bar over five corpora, as an MCP tool (BLI-3728).
+ * `tower_search` — one bar over every corpus, as an MCP tool (BLI-3728).
  *
  * The same `GET /api/search` door the browser's search bar and `cockpit
  * search` press, over this machine's device token

package/dist/search-tool.js

@@ -1,5 +1,5 @@
 /**
- * `tower_search` — one bar over five corpora, as an MCP tool (BLI-3728).
+ * `tower_search` — one bar over every corpus, as an MCP tool (BLI-3728).
  *
  * The same `GET /api/search` door the browser's search bar and `cockpit
  * search` press, over this machine's device token
@@ -25,10 +25,10 @@
 import { z } from "zod";
 import { loadAgentDoorSession } from "./agent-door-session.js";
 import { callAgentDoor } from "./agent-door.js";
-// Mirrors `SEARCH_KINDS` in apps/dashboard/src/lib/search/contracts.ts.
-// BLI-3880 added mail and cal; nothing in the type system ties the two
-// lists together, so `search-tool.test.ts` pins this one against the door.
-const KINDS = ["doc", "msg", "issue", "note", "mail", "cal", "memory"];
+// What `kinds` may name is the SERVER's to say (BLI-13027): this used to be a
+// z.enum copy of the dashboard's list, so an installed MCP server refused a
+// corpus the day it shipped. Kinds are forwarded as typed; the door answers
+// `unknown_kind` with the list, and `categories: true` asks for it up front.
 const KIND_LABELS = {
     doc: "Document",
     msg: "Message",
@@ -37,6 +37,8 @@ const KIND_LABELS = {
     mail: "Email",
     cal: "Calendar event",
     memory: "Memory",
+    scout: "Scout card",
+    careers: "Applicant",
 };
 function textResult(text, structured) {
     return {
@@ -51,13 +53,22 @@ export function registerSearchTool(server, deps) {
     const register = server.registerTool.bind(server);
     register("tower_search", {
         title: "Search everything in Tower",
-        description: "One search over documents, messages, Tower tickets, meeting notes, the caller's own mail, their calendar and BLI Memory. Use it when you know WHAT you are looking for but not WHERE it lives. Every result names the corpus it came from and where to open it; a memory has no page, so its text is the whole record. Mail and calendar are the caller's OWN — their mailboxes, their calendars and the ones shared with the organisation — never the whole company's. A calendar hit is the stored event, so a recurring meeting comes back once as its series rather than once per occurrence. A corpus that could not answer is reported separately from one that found nothing — do not read a failure as silence.",
+        description: "One search over Tower tickets, documents, meeting notes, messages, the caller's own mail, their calendar, BLI Memory, Scout and (only where the caller may read applications) Careers. Use it when you know WHAT you are looking for but not WHERE it lives. Every result names the corpus it came from and where to open it; a memory has no page, so its text is the whole record. Mail and calendar are the caller's OWN — their mailboxes, their calendars and the ones shared with the organisation — never the whole company's. A calendar hit is the stored event, so a recurring meeting comes back once as its series rather than once per occurrence. A corpus that could not answer is reported separately from one that found nothing — do not read a failure as silence.",
         inputSchema: {
-            query: z.string().min(2).max(1000).describe("What to look for, in the words a person would type."),
+            query: z
+                .string()
+                .min(2)
+                .max(1000)
+                .optional()
+                .describe("What to look for, in the words a person would type. Required unless categories is true."),
             kinds: z
-                .array(z.enum([...KINDS, "ticket"]))
+                .array(z.string().min(1).max(40))
+                .optional()
+                .describe("Narrow to these categories (issue, doc, note, msg, mail, cal, memory, scout, careers; ticket works for issue). Omit to search every one. Call with categories: true for the exact list this account is offered."),
+            categories: z
+                .boolean()
                 .optional()
-                .describe("Narrow to these corpora. Omit to search every one."),
+                .describe("True returns the categories this account can narrow to, instead of searching."),
             limit: z.number().int().min(1).max(50).optional().describe("Results to return (default 20)."),
         },
     }, async (args) => {
@@ -66,10 +77,15 @@ export function registerSearchTool(server, deps) {
         if (!loaded.ok) {
             return errorResult(`This machine is not paired with Tower (${loaded.reason}). ${loaded.message}`);
         }
+        if (args.categories === true)
+            return await listCategories(loaded.session, deps);
         const query = String(args.query ?? "");
+        if (query.trim().length < 2) {
+            return errorResult("tower_search needs a query of at least 2 characters, or categories: true to list the categories.");
+        }
         const params = new URLSearchParams({ q: query });
         if (Array.isArray(args.kinds) && args.kinds.length > 0) {
-            params.set("kinds", args.kinds.map((kind) => (kind === "ticket" ? "issue" : kind)).join(","));
+            params.set("kinds", args.kinds.map((kind) => kind.trim().toLowerCase()).join(","));
         }
         if (typeof args.limit === "number")
             params.set("limit", String(args.limit));
@@ -94,6 +110,26 @@ export function registerSearchTool(server, deps) {
         });
     });
 }
+/** `categories: true` — the list the browser's Command-K chips are drawn from. */
+async function listCategories(session, deps) {
+    const response = await callAgentDoor(session, deps.fetchImpl, "GET", "/api/search?categories=1");
+    if (!response.ok) {
+        if (response.transportError) {
+            return errorResult(`Tower could not be reached for tower_search (${response.transportError}). The categories were not read.`);
+        }
+        const reason = typeof response.body.reason === "string" ? response.body.reason : "unknown_error";
+        return errorResult(`Tower refused tower_search categories (${reason}).`);
+    }
+    const categories = (Array.isArray(response.body.categories) ? response.body.categories : []);
+    const lines = [
+        `${categories.length} categories this account can search. Name them in kinds; omit kinds to search all of them.`,
+        ...categories.map((entry) => {
+            const aliases = (entry.aliases ?? []).length > 0 ? ` (also: ${(entry.aliases ?? []).join(", ")})` : "";
+            return `- ${entry.kind}: ${entry.label}${aliases}`;
+        }),
+    ];
+    return textResult(lines.join("\n"), { categories });
+}
 /**
  * The sentence a model reads.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bli-cockpit/mcp",
-  "version": "0.1.104",
+  "version": "0.1.105",
   "private": false,
   "description": "bli-tower: an MCP server over BLI Cockpit's agent doors: JARVIS (jarvis_*), documents (docs_*), channels (msg_*), issues (work_*), the daily page (brief_*), meeting notes (notes_*), the ops board (ops_status/slack_*), settings/team/model, Scout and the workbook, plus the legacy event-stream tools (emit_event, get_ticket_timeline, get_active_tickets).",
   "type": "module",