Inspect recent browser network requests (DevTools-like). Use for debugging HTTP failures (4xx/5xx), payloads, and request sequences. Note: This captures network errors that console tools miss.

Interact with the active browser tab using semantic selectors (data-testid, role+name, label, placeholder, name, text, css, xpath). Supports actions: click, type, select, check/uncheck, keypress, hover, waitForSelector, scroll. Automatically scrolls into view and waits for visibility/enabled. Uses a CDP fallback in the extension when needed.

List all API tags with operation counts (from Swagger/OpenAPI).

Capture current browser tab; saves to structured path and returns image. Requires extension connection with DevTools open.

Enhanced UI Debugging Context Tool - Gets comprehensive debugging information for the element selected in browser DevTools.

Prerequisite: DevTools open, element selected in Elements panel.

Returns:

• Computed CSS styles - All applied styles for layout debugging

• Parent/child context - Understanding element relationships and layout flow

• Layout debugging info - Automatic detection of common CSS issues with actionable suggestions

• Accessibility audit - ARIA attributes, focus management, semantic information

• Interactive state - Hover, focus, click handlers, event listeners

• Material-UI context - Component type, variants, theme integration (when applicable)

• Performance hints - Large images, deep nesting, optimization opportunities

Autonomous AI Usage: This tool provides enough context to understand and fix UI issues without additional tool calls. Use the layoutDebug.issues and layoutDebug.suggestions arrays for immediate actionable insights.

Best used in workflow: Screenshot → Select Element → Enhanced Inspect → Apply Fixes

Execute a live HTTP request to API_BASE_URL; optionally include an Authorization bearer token retrieved from configured browser storage. Use after 'api.searchEndpoints' or for known endpoints.

Semantic API documentation search returning essential info: path, method, params (GET), request body (POST/PUT/PATCH/DELETE), and success responses. If schemas are missing, suggests using 'api.request' for live testing.

Navigates the current active browser tab to a new URL. Use for automated testing, navigation flows, or redirecting to specific pages. Requires Chrome extension to be connected.

Route Reference: ROUTES_FILE_PATH variable is not set so make sure you know the routes to use

Read browser console logs with filters; returns formatted summary + stats. Captures JS errors/warnings/logs and browser-generated network errors (e.g., 'Failed to load resource'). For full HTTP payloads and headers, use 'browser.network.inspect'.