@agentistics/mcp 2.25.1 → 2.26.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/agentistics-mcp.js +3 -12
- package/package.json +1 -1
package/dist/agentistics-mcp.js
CHANGED
|
@@ -684,7 +684,7 @@ var TOOLS = [
|
|
|
684
684
|
},
|
|
685
685
|
{
|
|
686
686
|
name: "agentistics_task_session",
|
|
687
|
-
description: "BETA — the task board is new and still changing; its shapes may move between releases. File a SESSION under a
|
|
687
|
+
description: "BETA — the task board is new and still changing; its shapes may move between releases. File a SESSION under a task, which is what makes the task measurable: its cost, tokens, rounds and harness all come from the sessions filed under it. Pass `subtaskId` to file it under one of the task's subtasks (the unit of WORK, for a task broken into steps); omit it to file the session directly on the task itself (the unit of DELIVERY, for a task simple enough not to need subtasks). Both can be used on the same task — some sessions direct, some under subtasks — and each subtask's own rollup plus the directly-filed sessions' own rollup are both readable via agentistics_task's `subtaskRollups` (keyed by subtask id, with `id: null` for the direct ones), so the breakdown never disappears. Use agentistics_task to read the subtasks, or agentistics_task_subtask to create one, then pass `ref` + `sessionId` (a managed session id or conversation id) + optionally `subtaskId`. Pass `detach` with a session id to unfile one. The task inherits the session's repository when it has none.",
|
|
688
688
|
inputSchema: {
|
|
689
689
|
type: "object",
|
|
690
690
|
properties: {
|
|
@@ -692,7 +692,7 @@ var TOOLS = [
|
|
|
692
692
|
sessionId: { type: "string" },
|
|
693
693
|
subtaskId: {
|
|
694
694
|
type: "string",
|
|
695
|
-
description: "The subtask to file it under.
|
|
695
|
+
description: "The subtask to file it under. Optional — omit to file the session directly on the task itself."
|
|
696
696
|
},
|
|
697
697
|
detach: { type: "string" }
|
|
698
698
|
},
|
|
@@ -1020,18 +1020,9 @@ server.setRequestHandler(CallToolRequestSchema, async (req) => {
|
|
|
1020
1020
|
return { content: [{ type: "text", text: JSON.stringify(body, null, 2) }] };
|
|
1021
1021
|
}
|
|
1022
1022
|
const ref = encodeURIComponent(String(a?.ref ?? ""));
|
|
1023
|
-
if (!a?.subtaskId) {
|
|
1024
|
-
return {
|
|
1025
|
-
content: [{
|
|
1026
|
-
type: "text",
|
|
1027
|
-
text: "A session is filed under a SUBTASK, never under the delivery itself — a task is the " + "unit of delivery, a subtask the unit of work. Read the parts with agentistics_task, or " + "create one with agentistics_task_subtask, then call this again with `subtaskId`."
|
|
1028
|
-
}],
|
|
1029
|
-
isError: true
|
|
1030
|
-
};
|
|
1031
|
-
}
|
|
1032
1023
|
const body = await apiSend("POST", `/api/tasks/${ref}/sessions`, {
|
|
1033
1024
|
sessionId: a?.sessionId,
|
|
1034
|
-
subtaskId: a.subtaskId
|
|
1025
|
+
...a?.subtaskId ? { subtaskId: a.subtaskId } : {}
|
|
1035
1026
|
});
|
|
1036
1027
|
return { content: [{ type: "text", text: JSON.stringify(body, null, 2) }] };
|
|
1037
1028
|
}
|