@ateam-ai/mcp 0.4.79 → 0.4.81

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ateam-ai/mcp",
-  "version": "0.4.79",
+  "version": "0.4.81",
   "mcpName": "io.github.ariekogan/ateam-mcp",
   "description": "A-Team MCP Server — build, validate, and deploy multi-agent solutions from any AI environment",
   "type": "module",

package/src/tools.js

@@ -658,7 +658,7 @@ export const tools = [
     // it times out the run proceeds with no capability guidance at all.
     monitoring: { safe: true, cost: "normal", latency_ms_p95: 25000, output: "bounded" },
     description:
-      "CONSULT THIS DURING DESIGN — before and while you design a skill/solution. Describe what you're building; it returns POINTERS to the platform capabilities that fit (per-actor storage, widgets, triggers, sub-agents, mobile data, run-scripts, multi-skill, GitHub, …), each with the /spec topic to read next (via ateam_get_spec) and the tool to wire it. Also returns 'missing' hints (capabilities your goal implies but the design hasn't wired) and lifecycle hints (e.g. connect GitHub when the project will iterate). ADVISORY ONLY — you decide and own the design. Stateless: pass the current design_state each call; consult it as often as you like as the design evolves.",
+      "CONSULT THIS DURING DESIGN — before and while you design a skill/solution. Describe what you're building; it returns POINTERS to the platform capabilities that fit (per-actor storage, widgets, triggers, sub-agents, mobile data, run-scripts, multi-skill, GitHub, …), each with the /spec topic to read next (via ateam_get_spec) and the tool to wire it. Also returns 'missing' hints (capabilities your goal implies but the design hasn't wired) and lifecycle hints (e.g. connect GitHub when the project will iterate). ADVISORY ONLY — you decide and own the design. Stateless: pass the current design_state each call; consult it as often as you like as the design evolves. If the reply carries `truncated: true`, the answer ran past the length budget and was CUT OFF: what is there is correct, but a capability's ABSENCE proves nothing — ask again with a narrower goal, or use ateam_spec_search, before concluding the platform lacks something.",
     inputSchema: {
       type: "object",
       properties: {
@@ -4966,7 +4966,25 @@ const handlers = {
       throw new Error("Pass chain_id (the whole run — recommended) or job_id. ateam_conversation returns chain_id.");
     }
     if (!skill_id) {
-      throw new Error(`job_id "${job_id}" needs skill_id too — the per-job endpoint is scoped by skill. Pass chain_id instead to poll the whole run without knowing which skill ran it.`);
+      // ASK FOR NOTHING THE TOOL CAN WORK OUT ITSELF. This used to throw
+      // "job_id needs skill_id too — pass chain_id instead". The message was
+      // accurate and well-written, and it was reached by FAILING FIRST, every
+      // time: 4 occurrences on 4 different job ids in a single clean e2e, each
+      // one a wasted turn. A good error still costs a round trip.
+      //
+      // /deploy/jobs/:id/status resolves ANY job id — it is the same endpoint
+      // the chain path above already uses — so a job id without a skill needs no
+      // skill at all. `scope` says which question was answered, because "this
+      // job" and "the whole run" genuinely differ: a root job can read completed
+      // while a handoff is still running.
+      const data = await get(`/deploy/jobs/${encodeURIComponent(job_id)}/status`, sid);
+      return {
+        ok: true,
+        scope: "job",
+        job_id,
+        ...data,
+        _note: `Answered for THIS JOB. For the whole run — including handoffs a root job does not cover — pass chain_id instead${data?.chainId ? ` (this job's chain is "${data.chainId}")` : ""}.`,
+      };
     }
     // Existing single-job snapshot via Builder (unchanged shape for back-compat).
     const single = await get(`/deploy/solutions/${solution_id}/skills/${skill_id}/test/${job_id}`, sid);