@ateam-ai/mcp 0.4.44 → 0.4.46

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ateam-ai/mcp",
-  "version": "0.4.44",
+  "version": "0.4.46",
   "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/api.js

@@ -461,7 +461,21 @@ function formatError(method, path, status, body, baseUrl) {
   }
 
   const hint = hints[status] || "";
-  const detail = typeof body === "string" && body.length > 0 && body.length < 2000 ? body : "";
+  // A JSON error body used to be dropped entirely — only a string body became
+  // `detail`. So an endpoint that answers 4xx WITH the diagnosis (ui.surfaceProbe
+  // returns 422 + the failures that explain why the surface is broken) reached
+  // the caller as a bare "returned 422", throwing away the very thing it was
+  // asked to produce. Serialize objects too, capped the same way.
+  let detail = "";
+  const asText = typeof body === "string"
+    ? body
+    : (body && typeof body === "object" ? (() => { try { return JSON.stringify(body); } catch { return ""; } })() : "");
+  if (asText.length > 0) {
+    // Previously a body of 2000+ chars was dropped ENTIRELY, so the richer the
+    // error the less the caller was told — a 422 carrying the full diagnosis
+    // arrived as a bare status code. Truncate instead of discarding.
+    detail = asText.length < 2000 ? asText : asText.slice(0, 2000) + "… (truncated)";
+  }
 
   // Always show the FULL URL actually hit — ateam-mcp is a PUBLIC MCP with a
   // configurable base (prod default, dev/self-host overrides), so a bare
@@ -525,6 +539,12 @@ async function request(method, path, body, sessionId, opts = {}) {
         // on this to NOT scaffold-clobber an existing skill on a read error.
         const e = new Error(formatError(method, path, res.status, text, baseUrl));
         e.status = res.status;
+        // Keep the RAW body on the error. formatError truncates for humans, and
+        // an endpoint that answers 4xx WITH the diagnosis (ui.surfaceProbe's 422
+        // carries the failures explaining why a surface is broken) is exactly the
+        // case where the body matters more than the status. A caller that knows
+        // how to read its own error shape should not have to scrape a message.
+        e.body = text;
         throw e;
       }
 

package/src/tools.js

@@ -4036,10 +4036,25 @@ const handlers = {
     if (actor_id) body.actor_id = actor_id;
     // Forwards to the skill-validator, which runs Core's ui.surfaceProbe via /mcp.
     // 60s: navigate + settle + warm-retry inside Core, plus the hop.
-    return await post(
-      `/deploy/solutions/${solution_id}/plugins/${encodeURIComponent(plugin_id)}/verify-surface`,
-      body, sid, { timeoutMs: 60000 }
-    );
+    try {
+      return await post(
+        `/deploy/solutions/${solution_id}/plugins/${encodeURIComponent(plugin_id)}/verify-surface`,
+        body, sid, { timeoutMs: 60000 }
+      );
+    } catch (err) {
+      // A FAILING surface is this tool's whole job, not a transport error. The
+      // route maps a negative verdict to 422 (503 for inconclusive), which the
+      // generic error path turned into "returned 422" — hiding the failures that
+      // say WHY the screen is broken, and leaving the caller as blind as before
+      // it ran the probe. Hand the verdict back as a result instead of throwing.
+      if (typeof err?.body === "string" && err.body) {
+        try {
+          const parsed = JSON.parse(err.body);
+          if (parsed && (parsed.verdict || Array.isArray(parsed.failures))) return parsed;
+        } catch { /* not the probe's body — fall through */ }
+      }
+      throw err;
+    }
   },
 
   ateam_test_skill: async ({ solution_id, skill_id, message, wait, wait_for, chain_timeout_ms, actor_id }, sid) => {