@bli-cockpit/mcp 0.1.103 → 0.1.104

package/dist/search-tool.js

@@ -32,7 +32,7 @@ const KINDS = ["doc", "msg", "issue", "note", "mail", "cal", "memory"];
 const KIND_LABELS = {
     doc: "Document",
     msg: "Message",
-    issue: "Issue",
+    issue: "Ticket",
     note: "Meeting note",
     mail: "Email",
     cal: "Calendar event",
@@ -51,11 +51,11 @@ 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, issues, 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 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.",
         inputSchema: {
             query: z.string().min(2).max(1000).describe("What to look for, in the words a person would type."),
             kinds: z
-                .array(z.enum(KINDS))
+                .array(z.enum([...KINDS, "ticket"]))
                 .optional()
                 .describe("Narrow to these corpora. Omit to search every one."),
             limit: z.number().int().min(1).max(50).optional().describe("Results to return (default 20)."),
@@ -69,7 +69,7 @@ export function registerSearchTool(server, deps) {
         const query = String(args.query ?? "");
         const params = new URLSearchParams({ q: query });
         if (Array.isArray(args.kinds) && args.kinds.length > 0) {
-            params.set("kinds", args.kinds.join(","));
+            params.set("kinds", args.kinds.map((kind) => (kind === "ticket" ? "issue" : kind)).join(","));
         }
         if (typeof args.limit === "number")
             params.set("limit", String(args.limit));

package/dist/work-tools.js

@@ -84,13 +84,13 @@ async function resolveParentId(deps, session, ref) {
 export function registerWorkTools(server, deps) {
     const register = registrarFor(server);
     register("work_list_issues", {
-        title: "List Tower issues",
-        description: "Issues you may see, most recently updated first: identifier, state, title, priority, assignee, project. "
+        title: "List Tower tickets",
+        description: "Tower tickets you may see, most recently updated first: identifier, state, title, priority, assignee, project. "
             + "Filter by state, assignee (\"me\", \"unassigned\", or a uuid) or project (name or uuid). "
-            + `Default ${DEFAULT_LIST_LIMIT} issues; the answer says when more exist. `
-            + "Never a description — call work_get_issue for one issue's full text.",
+            + `Default ${DEFAULT_LIST_LIMIT} tickets; the answer says when more exist. `
+            + "Never a description — call work_get_issue for one ticket's full text.",
         inputSchema: {
-            state: z.enum(WORK_ISSUE_STATES).optional().describe("Only issues in this state."),
+            state: z.enum(WORK_ISSUE_STATES).optional().describe("Only tickets in this state."),
             assignee: z.string().min(1).max(100).optional().describe('"me", "unassigned", or a person\'s uuid.'),
             project: z.string().min(1).max(200).optional().describe("A project name or uuid."),
             limit: z.number().int().min(1).max(ISSUE_LIST_MAX).optional().describe(`At most this many issues. Default ${DEFAULT_LIST_LIMIT}.`),
@@ -144,8 +144,8 @@ export function registerWorkTools(server, deps) {
         });
     }));
     register("work_get_issue", {
-        title: "Read a Tower issue",
-        description: "One issue's title, state, priority, assignee (name and email, not just its id), description and every "
+        title: "Read a Tower ticket",
+        description: "One Tower ticket's title, state, priority, assignee (name and email, not just its id), description and every "
             + "comment on it. `ids` reads several in one call — still one request per issue plus its comments, "
             + "no bulk door exists yet. A single id answers `{ issue, comments }`; several answer "
             + "`{ issues: [{ ref, ok, issue, comments } | { ref, ok: false, error, detail }] }` so one bad id never "
@@ -189,8 +189,8 @@ export function registerWorkTools(server, deps) {
         });
     }));
     register("work_create_issue", {
-        title: "File a Tower issue",
-        description: "Files a new issue and returns the BLI-#### identifier it was given. Use this the way you would file a Linear ticket.",
+        title: "File a Tower ticket",
+        description: "Files a new Tower ticket and returns the BLI-#### identifier it was given. Use this the way you would file a Linear ticket.",
         inputSchema: {
             title: z.string().min(1).max(300).describe("The issue title."),
             description: z.string().max(200_000).optional().describe("The issue body, markdown."),
@@ -236,8 +236,8 @@ export function registerWorkTools(server, deps) {
         return textResult(`Filed ${issue?.identifier ?? ""} — ${issue?.title ?? ""} (${issue?.id ?? ""}).`, { issue: issue ? withSizeLabel(issue) : issue });
     }));
     register("work_update_issue", {
-        title: "Update a Tower issue",
-        description: "Changes an issue's title, description, priority, assignee or project. Only the fields you pass change. "
+        title: "Update a Tower ticket",
+        description: "Changes a Tower ticket's title, description, priority, assignee or project. Only the fields you pass change. "
             + "State does NOT move here — call work_move_issue, which records the move.",
         inputSchema: {
             id: ISSUE_REF,
@@ -285,8 +285,8 @@ export function registerWorkTools(server, deps) {
         return textResult(`Updated ${issue?.identifier ?? ref} — ${issue?.title ?? ""}.`, { issue: issue ? withSizeLabel(issue) : issue });
     }));
     register("work_move_issue", {
-        title: "Move a Tower issue",
-        description: "Moves an issue to a new state and records the move in its history. This is how an issue's state changes; "
+        title: "Move a Tower ticket",
+        description: "Moves a Tower ticket to a new state and records the move in its history. This is how a ticket's state changes; "
             + "there is no other door.",
         inputSchema: { id: ISSUE_REF, state: z.enum(WORK_ISSUE_STATES).describe("The state to move it to.") },
     }, async (args) => withSession(deps, async (session) => {
@@ -300,8 +300,8 @@ export function registerWorkTools(server, deps) {
         return textResult(`${issue?.identifier ?? ref} is now ${issue?.state ?? String(args.state)}.`, { issue });
     }));
     register("work_comment_issue", {
-        title: "Comment on a Tower issue",
-        description: "Posts a comment. Comments are append-only — nothing here edits or deletes one.",
+        title: "Comment on a Tower ticket",
+        description: "Posts a comment on a Tower ticket. Comments are append-only — nothing here edits or deletes one.",
         inputSchema: { id: ISSUE_REF, body_markdown: z.string().min(1).max(50_000).describe("The comment, markdown.") },
     }, async (args) => withSession(deps, async (session) => {
         const ref = String(args.id ?? "");
@@ -312,8 +312,8 @@ export function registerWorkTools(server, deps) {
         return textResult(`Commented on ${ref} (${comment?.id ?? "?"}).`, { comment });
     }));
     register("work_issue_history", {
-        title: "Read a Tower issue's history",
-        description: "Every recorded change to one issue — state moves, assignee changes — newest first, with who made it and "
+        title: "Read a Tower ticket's history",
+        description: "Every recorded change to one Tower ticket — state moves, assignee changes — newest first, with who made it and "
             + "when. History rows are never rewritten; a row imported without state names says so rather than showing "
             + "\"(none) -> (none)\".",
         inputSchema: {
@@ -336,7 +336,7 @@ export function registerWorkTools(server, deps) {
     }));
     register("work_list_projects", {
         title: "List Tower projects",
-        description: "The projects issues are filed under. Use a project's name with work_list_issues or work_create_issue.",
+        description: "The projects Tower tickets are filed under. Use a project's name with work_list_issues or work_create_issue.",
         inputSchema: { include_archived: z.boolean().optional().describe("true: archived projects too.") },
     }, async (args) => withSession(deps, async (session) => {
         const response = await callAgentDoor(session, deps.fetchImpl, "GET", `/api/work/projects${args.include_archived ? "?include_archived=true" : ""}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bli-cockpit/mcp",
-  "version": "0.1.103",
+  "version": "0.1.104",
   "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",