@ateam-ai/mcp 0.4.12 → 0.4.13
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/package.json +1 -1
- package/src/tools.js +3 -2
package/package.json
CHANGED
package/src/tools.js
CHANGED
|
@@ -435,8 +435,9 @@ export const tools = [
|
|
|
435
435
|
core: true,
|
|
436
436
|
description:
|
|
437
437
|
"Send a chat message to a deployed solution. No skill_id needed — the system auto-routes to the right skill.\n\n" +
|
|
438
|
-
"ALWAYS ASYNC: returns a
|
|
439
|
-
"
|
|
438
|
+
"ALWAYS ASYNC: returns a chain_id immediately — the assistant's reply is NOT in this response (a conversation can run for minutes across handoffs + subcalls, so a synchronous wait would hit the 100s edge timeout → 524).\n\n" +
|
|
439
|
+
"POLL BY CHAIN, NEVER BY JOB: an individual job can terminate while the chain is still running, so poll ateam_chain_status(chain_id) on a loop (~2s) and stop when chain_done === true (or pending_question is set — the assistant is waiting on the user). That is the cheap chip-quick poll (Core's whole-chain computeChainStatus — the same thing the standard chat uses). Use ateam_get_chain(chain_id) only ONCE at the end if you want the full tree / per-job detail — it's too heavy to loop on.\n\n" +
|
|
440
|
+
"Multi-turn: pass the actor_id from a previous response back in to continue the same thread (e.g. reply to a confirmation prompt). Each call starts a new chain; the same actor_id maintains conversation context.",
|
|
440
441
|
inputSchema: {
|
|
441
442
|
type: "object",
|
|
442
443
|
properties: {
|