@debugg-ai/debugg-ai-mcp 3.1.0 → 3.2.0

package/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to the DebuggAI MCP project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.2.0]
+
+### Added — Structured tool output (`structuredContent`)
+
+Every successful tool result now carries [`structuredContent`](https://modelcontextprotocol.io/specification/2025-06-18/server/tools)
+— the parsed JSON payload — so clients can consume structured data directly
+instead of re-parsing the text blob. The text block is kept for back-compat.
+
+Promoted centrally in the CallTool path (`withStructuredContent` in
+`utils/structuredContent.ts`) rather than touching every handler. No-op for
+errors, non-object payloads, or multi-text results.
+
+`outputSchema` is intentionally not declared: the action tools return
+polymorphic shapes per action, a faithful schema would need top-level `oneOf`
+(which the Anthropic API rejects), and a permissive schema adds no value.
+`structuredContent` without a declared schema is spec-valid and is the win.
+
 ## [3.1.0]
 
 ### Added — Tool annotations (behavioral hints for clients)

package/dist/index.js

@@ -21,7 +21,7 @@ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
 import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
 import { config } from "./config/index.js";
 import { initTools, getTools, getTool } from "./tools/index.js";
-import { Logger, validateInput, createErrorResponse, toMCPError, handleConfigurationError, Telemetry, TelemetryEvents, } from "./utils/index.js";
+import { Logger, validateInput, createErrorResponse, toMCPError, handleConfigurationError, Telemetry, TelemetryEvents, withStructuredContent, } from "./utils/index.js";
 import { MCPErrorCode, MCPError, } from "./types/index.js";
 // Logger and server are initialized lazily in main() to avoid triggering
 // config loading at module load time. If config validation fails (bad env vars),
@@ -116,7 +116,8 @@ function registerHandlers() {
             const toolDuration = Date.now() - toolStart;
             requestLogger.info(`Tool execution completed: ${name}`);
             Telemetry.capture(TelemetryEvents.TOOL_EXECUTED, { toolName: name, durationMs: toolDuration, success: true });
-            return result;
+            // Promote the JSON text payload to structuredContent (back-compat: text stays).
+            return withStructuredContent(result);
         }
         catch (error) {
             const mcpError = toMCPError(error, 'tool execution');

package/dist/utils/index.js

@@ -7,3 +7,4 @@ export * from './errors.js';
 export * from './projectAnalyzer.js';
 export * from './imageUtils.js';
 export * from './telemetry.js';
+export * from './structuredContent.js';

package/dist/utils/structuredContent.js

@@ -0,0 +1,42 @@
+/**
+ * Structured tool output (epic 3eb5l).
+ *
+ * MCP 2025-06-18 added `structuredContent` on tool results: a machine-readable
+ * JSON object that mirrors the human-readable text block. Clients that support
+ * it consume parsed data directly instead of re-parsing the text blob; the text
+ * block stays for back-compat.
+ *
+ * Every leaf handler already returns its payload as `JSON.stringify(payload)` in
+ * a single text item, so rather than touch ~20 handlers we promote it in ONE
+ * place — the CallTool path in index.ts wraps each result with this helper.
+ *
+ * We intentionally do NOT declare `outputSchema` on the tools: the action tools
+ * return polymorphic shapes per action, a faithful schema would need top-level
+ * `oneOf` (which the Anthropic API rejects, same as input schemas), and a
+ * permissive `type:object` schema adds no value. `structuredContent` without a
+ * declared schema is spec-valid and is the actual win.
+ */
+/**
+ * Attach `structuredContent` to a successful tool result when its single text
+ * block is a JSON object. No-op for errors, multi-text results, non-object
+ * payloads, or results that already set structuredContent.
+ */
+export function withStructuredContent(result) {
+    if (!result || result.isError || result.structuredContent)
+        return result;
+    const textItems = (result.content || []).filter((c) => c.type === 'text' && typeof c.text === 'string');
+    if (textItems.length !== 1)
+        return result;
+    let parsed;
+    try {
+        parsed = JSON.parse(textItems[0].text);
+    }
+    catch {
+        return result; // not JSON (shouldn't happen for our handlers) — leave as-is
+    }
+    // Spec requires structuredContent to be a JSON object (not array/primitive/null).
+    if (parsed === null || typeof parsed !== 'object' || Array.isArray(parsed)) {
+        return result;
+    }
+    return { ...result, structuredContent: parsed };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@debugg-ai/debugg-ai-mcp",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Zero-Config, Fully AI-Managed End-to-End Testing for all code gen platforms.",
   "type": "module",
   "bin": {