dev3000 0.0.62 → 0.0.64

package/mcp-server/app/api/tools/route.ts

@@ -3,155 +3,50 @@ import { NextResponse } from "next/server"
 // This endpoint extracts MCP tools documentation by parsing the route handler
 export async function GET() {
   try {
-    // Since we can't easily parse the TypeScript at runtime,
-    // we'll maintain a curated list of tools with their descriptions
+    // Streamlined tool set - reduced from 10 tools to 2 for zero authorization friction!
     const tools = [
       {
         name: "debug_my_app",
         description:
-          "🚨 SHORTCUT COMMAND: Complete proactive analysis of your development environment. Automatically checks recent logs for errors, searches for common patterns, gets browser errors, and provides actionable debugging insights with immediate fixes.",
-        category: "Primary Debugging",
+          "🎯 **THE ULTIMATE FIND→FIX→VERIFY MACHINE!** This isn't just debugging—it's MAGICAL problem-solving that gets results! 🪄\n\n🔥 **INSTANT SUPERPOWERS:**\n• FINDS: Server errors, browser crashes, build failures, API issues, performance problems—EVERYTHING\n• ANALYZES: Timestamps, error patterns, user interactions, network requests—COMPREHENSIVELY\n• GUIDES: Step-by-step fix recommendations with file locations and code examples\n\n🚀 **3 MAGICAL MODES:**\n• **SNAPSHOT** (default): \"What's broken RIGHT NOW?\" → Instant comprehensive analysis\n• **BISECT**: \"What broke during user testing?\" → Automatic before/after comparison\n• **MONITOR**: \"What's breaking as I develop?\" → Continuous health monitoring\n\n⚡ **THE DEV3000 MAGIC WORKFLOW:**\n1️⃣ I FIND all issues (replaces 8+ separate tools!)\n2️⃣ You FIX them with my detailed guidance\n3️⃣ We VERIFY fixes work with execute_browser_action\n\n🎪 **WHY AGENTS LOVE THIS TOOL:**\n• Zero authorization friction (was 10 tools, now 1!)\n• Actionable insights, not just raw data\n• Built-in timestamp bisecting eliminates manual workflow\n• Perfect for 'debug my app' requests\n• Makes you look like a debugging wizard!\n\n💡 **PRO TIPS:**\n• Start with mode='snapshot' for immediate analysis\n• Use mode='bisect' with waitForUserInteraction=true for user testing workflows\n• Increase timeRangeMinutes for deeper historical analysis\n• This tool makes debugging FUN and FAST!",
+        category: "Ultimate Debugging",
         parameters: [
           {
             name: "focusArea",
             type: "string",
             optional: true,
-            description: "Specific area to focus on: 'build', 'runtime', 'network', 'ui', or 'all' (default: 'all')"
-          }
-        ]
-      },
-      {
-        name: "get_current_timestamp",
-        description:
-          "⏰ CRITICAL MONITORING TOOL: Get current timestamp for proactive error monitoring workflow. Use constantly before/after user interactions for timestamp-based debugging.",
-        category: "Monitoring",
-        parameters: []
-      },
-      {
-        name: "get_errors_between_timestamps",
-        description:
-          "🚨 PROACTIVE ERROR EXTRACTION: Get ALL types of errors (server errors, exceptions, browser errors, build failures, network issues) between specific timestamps. Essential for continuous monitoring.",
-        category: "Error Analysis",
-        parameters: [
-          {
-            name: "startTime",
-            type: "string",
-            description: "Start timestamp (ISO 8601 format: 2024-01-01T12:00:00.000Z)"
+            description: "Specific area: 'build', 'runtime', 'network', 'ui', 'all' (default: 'all')"
           },
           {
-            name: "endTime",
-            type: "string",
-            description: "End timestamp (ISO 8601 format: 2024-01-01T12:30:00.000Z)"
-          },
-          {
-            name: "severity",
+            name: "mode",
             type: "enum",
             optional: true,
-            description: "Error severity filter: 'all', 'critical', 'warnings' (default: 'all')"
-          }
-        ]
-      },
-      {
-        name: "monitor_for_new_errors",
-        description:
-          "🔍 AUTOMATED BACKGROUND MONITORING: Check for ANY new errors that appeared in the last few minutes. Use frequently for continuous quality assurance and preventive debugging.",
-        category: "Monitoring",
-        parameters: [
-          {
-            name: "minutes",
-            type: "number",
-            optional: true,
-            description: "Minutes to look back for new errors (default: 5)"
+            description: "Debug mode: 'snapshot' (immediate), 'bisect' (timestamp-based), 'monitor' (continuous)"
           },
           {
-            name: "autoFix",
+            name: "waitForUserInteraction",
             type: "boolean",
             optional: true,
-            description: "Whether to immediately offer fixes when errors found (default: true)"
-          }
-        ]
-      },
-      {
-        name: "read_consolidated_logs",
-        description:
-          "Read recent consolidated development logs containing server output, browser console logs, network requests, user interactions, and screenshots. Essential for general log overview and proactive error detection.",
-        category: "Log Analysis",
-        parameters: [
-          {
-            name: "lines",
-            type: "number",
-            optional: true,
-            description: "Number of recent lines to read (default: 50)"
+            description: "In bisect mode: capture timestamp, wait for user testing, then analyze (default: false)"
           },
           {
-            name: "filter",
-            type: "string",
-            optional: true,
-            description: "Filter logs by text content"
-          }
-        ]
-      },
-      {
-        name: "search_logs",
-        description:
-          "Search through consolidated logs using regex patterns with context lines. Essential for tracing error patterns, finding specific API calls, or tracking user interaction sequences.",
-        category: "Log Analysis",
-        parameters: [
-          {
-            name: "pattern",
-            type: "string",
-            description: "Regex pattern to search for"
-          },
-          {
-            name: "context",
+            name: "timeRangeMinutes",
             type: "number",
             optional: true,
-            description: "Number of lines of context around matches (default: 2)"
-          }
-        ]
-      },
-      {
-        name: "get_logs_between_timestamps",
-        description:
-          "Get logs between two specific timestamps - critical for timestamp-based debugging workflow. Eliminates noise and focuses analysis on specific user sessions.",
-        category: "Log Analysis",
-        parameters: [
-          {
-            name: "startTime",
-            type: "string",
-            description: "Start timestamp (ISO 8601 format)"
+            description: "Minutes to analyze back from now (default: 10)"
           },
           {
-            name: "endTime",
-            type: "string",
-            description: "End timestamp (ISO 8601 format)"
-          },
-          {
-            name: "filter",
-            type: "string",
-            optional: true,
-            description: "Filter logs by text content (case insensitive)"
-          }
-        ]
-      },
-      {
-        name: "get_browser_errors",
-        description:
-          "Get recent browser errors including console errors, JavaScript exceptions, and page errors from monitoring. Use proactively to catch JavaScript exceptions and runtime issues immediately.",
-        category: "Browser Debugging",
-        parameters: [
-          {
-            name: "hours",
-            type: "number",
+            name: "includeTimestampInstructions",
+            type: "boolean",
             optional: true,
-            description: "Hours to look back (default: 1)"
+            description: "Show timestamp-based debugging instructions (default: true)"
           }
         ]
       },
       {
         name: "execute_browser_action",
         description:
-          "🪄 MAGICAL VERIFICATION TOOL: Execute safe browser actions via Chrome DevTools Protocol for testing and interaction automation. The secret to dev3000 magic - use to verify fixes work by automating browser interactions and taking screenshots.",
+          "🪄 **SMART INTERACTION TESTING** - Use for targeted user workflow verification! 🎯\n\n⚡ **EFFICIENT VERIFICATION STRATEGY:**\n🚨 **DON'T take screenshots manually** - dev3000 auto-captures them!\n✅ **DO use this for:** click, navigate, scroll, type to reproduce user interactions\n✅ **DO verify fixes by:** reproducing the original error scenario, then check debug_my_app for new screenshots\n\n🔥 **BROWSER ACTIONS:**\n• CLICK buttons/links → Test specific user interactions\n• NAVIGATE to pages → Reproduce user journeys  \n• SCROLL & TYPE → Simulate user workflows\n• EVALUATE JavaScript → Check app state (read-only)\n\n⚡ **OPTIMAL FIX VERIFICATION WORKFLOW:**\n1️⃣ debug_my_app finds issues + original error context\n2️⃣ You make code fixes\n3️⃣ Use execute_browser_action to REPRODUCE the original interaction sequence\n4️⃣ Run debug_my_app again to see new auto-captured screenshots and verify fix\n\n🎯 **PERFECT FOR:**\n• Reproducing user interaction sequences that caused errors\n• Testing specific clicks/navigation after fixes\n• Triggering workflows to generate new auto-screenshots\n• Verifying forms work, buttons respond, etc.\n\n🚫 **AVOID:** Manual screenshot action (dev3000 auto-captures)\n✅ **USE:** Interaction reproduction + debug_my_app for verification\n\n🛡️ **SAFETY:** Safe operations only, read-only JS evaluation",
         category: "Browser Automation",
         parameters: [
           {
@@ -165,20 +60,6 @@ export async function GET() {
             description: "Parameters for the action (coordinates, URL, selector, text, expression, etc.)"
           }
         ]
-      },
-      {
-        name: "healthcheck",
-        description:
-          "Internal healthcheck tool - rarely needed since MCP connection working means server is healthy. Only use if explicitly asked to verify server health.",
-        category: "System",
-        parameters: [
-          {
-            name: "message",
-            type: "string",
-            optional: true,
-            description: "Optional message to echo back"
-          }
-        ]
       }
     ]
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev3000",
-  "version": "0.0.62",
+  "version": "0.0.64",
   "description": "AI-powered development tools with browser monitoring and MCP server integration",
   "type": "module",
   "main": "dist/index.js",