@agentistics/mcp 2.194.0 → 2.195.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 +5 -3
- package/package.json +1 -1
package/dist/agentistics-mcp.js
CHANGED
|
@@ -2453,20 +2453,21 @@ var TOOLS = [
|
|
|
2453
2453
|
},
|
|
2454
2454
|
{
|
|
2455
2455
|
name: "agentistics_session_message",
|
|
2456
|
-
description:
|
|
2456
|
+
description: 'Send a message to ANOTHER agentistics session — the standard channel between a session and the one that started it (or the ones it started). `to` is a session reference (managed id, conversation id, exact title or unique id prefix); `kind` is handback (work finished/committed), block (you cannot continue) or question (you need a decision); `body` is the text. It is typed into the target\'s own conversation through the same path its composer uses, headed `[from session <id> · <kind>]`, and — when YOUR session is filed on a task or subtask — also recorded there as a comment of that kind. Use it to report to the session that started you instead of asking the user; a parent may message its children the same way. Refused for a session that does not exist, for yourself, from a process that is not a verified agentop session, and more than once per 2 seconds to the same session. INTERMEDIATE handback: a handback is read by the runtime as "I finished everything" (the product may close you once you are stopped, clean and saved). If you stop on purpose between phases, waiting for a signal, pass `awaiting` (kind=handback only, one line ≤200 chars, e.g. "engine merged <sha>"): the runtime then refuses to close you while that is your newest handback. A later handback WITHOUT `awaiting` counts as final again.',
|
|
2457
2457
|
inputSchema: {
|
|
2458
2458
|
type: "object",
|
|
2459
2459
|
properties: {
|
|
2460
2460
|
to: { type: "string", description: "The target session reference." },
|
|
2461
2461
|
kind: { type: "string", enum: ["handback", "block", "question"] },
|
|
2462
|
-
body: { type: "string", description: "The message." }
|
|
2462
|
+
body: { type: "string", description: "The message." },
|
|
2463
|
+
awaiting: { type: "string", description: "kind=handback only: what you stopped waiting for (marks the handback as intermediate; the worker is not closed). Omit on a final handback." }
|
|
2463
2464
|
},
|
|
2464
2465
|
required: ["to", "kind", "body"]
|
|
2465
2466
|
}
|
|
2466
2467
|
},
|
|
2467
2468
|
{
|
|
2468
2469
|
name: "agentistics_wait",
|
|
2469
|
-
description: "EXPERIMENTAL (AGENTISTICS_FLOWS) — a DURABLE wait the SERVER keeps for YOU: instead of polling or running a background command, register what you wait for and a deadline; when the condition is met (or the deadline passes, once) the server types a wake message into your own session, headed `[from flow wait · nudge]`, naming the wait id and generation. Conditions are a closed set: `{kind:'handback', from:<session id>, since?:ISO}` (a handback FROM that session), `{kind:'memory', minAvailableMB}` (free memory, two stable readings), `{kind:'time', at:ISO}`, `{kind:'gate', gate:'sessao-parada'|'arvore-limpa'|'trabalho-salvo', sessionId}`. action=register needs `condition` + `deadlineAt` (ISO UTC, ≤30 days; pass `requestId` to make a retry the same wait); action=ack (`waitId`, `generation`) confirms you RECEIVED the wake — without it the wake is sent again (at most 3 times), so ack every wake, and treat a repeated wake for the same id+generation as already handled; action=cancel (`waitId`) before it fires; action=list your open waits; action=handoff (`from`: the previous leader on the same task) moves its waits to you. A wait is never 'working' nor an approval.",
|
|
2470
|
+
description: "EXPERIMENTAL (AGENTISTICS_FLOWS) — a DURABLE wait the SERVER keeps for YOU: instead of polling or running a background command, register what you wait for and a deadline; when the condition is met (or the deadline passes, once) the server types a wake message into your own session, headed `[from flow wait · nudge]`, naming the wait id and generation. Conditions are a closed set: `{kind:'handback', from:<session id>, since?:ISO, match?:text}` (a handback FROM that session; `match` = case-insensitive substring its text must contain, so another subject does not wake you), `{kind:'memory', minAvailableMB}` (free memory, two stable readings), `{kind:'time', at:ISO}`, `{kind:'gate', gate:'sessao-parada'|'arvore-limpa'|'trabalho-salvo', sessionId}`. action=register needs `condition` + `deadlineAt` (ISO UTC, ≤30 days; pass `requestId` to make a retry the same wait); action=ack (`waitId`, `generation`) confirms you RECEIVED the wake — without it the wake is sent again (at most 3 times), so ack every wake, and treat a repeated wake for the same id+generation as already handled; action=cancel (`waitId`) before it fires; action=list your open waits; action=handoff (`from`: the previous leader on the same task) moves its waits to you. A wait is never 'working' nor an approval.",
|
|
2470
2471
|
inputSchema: {
|
|
2471
2472
|
type: "object",
|
|
2472
2473
|
properties: {
|
|
@@ -3068,6 +3069,7 @@ async function callTool(req) {
|
|
|
3068
3069
|
to: a?.to,
|
|
3069
3070
|
kind: a?.kind,
|
|
3070
3071
|
body: a?.body,
|
|
3072
|
+
awaiting: a?.awaiting,
|
|
3071
3073
|
session: sessionProof(process.env)
|
|
3072
3074
|
});
|
|
3073
3075
|
return { content: [{ type: "text", text: JSON.stringify(body, null, 2) }] };
|
package/package.json
CHANGED