Skip to main content
Glama

get_all_debug_activity

Retrieve a combined feed of all debug events on the Firefox MCP Server, enabling detailed monitoring and troubleshooting of browser automation activities. Specify tab ID, time range, and event limit for precise debugging.

Instructions

Get combined feed of all debug events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sinceNo
tabIdNo

Implementation Reference

  • The core handler function for 'get_all_debug_activity'. Aggregates debug events from multiple sources (console, errors, network, WebSocket), sorts by timestamp, applies optional filters (since, limit), and returns a combined JSON feed.
    async getAllDebugActivity(args = {}) {
      const { tabId, since, limit = 100 } = args;
      const effectiveTabId = tabId || this.activeTabId;
      
      // Combine all debug events with timestamps
      const allEvents = [];
      
      // Console logs
      const logs = this.consoleLogs.get(effectiveTabId) || [];
      logs.forEach(log => allEvents.push({ ...log, source: 'console' }));
      
      // JavaScript errors
      const errors = this.jsErrors.get(effectiveTabId) || [];
      errors.forEach(error => allEvents.push({ ...error, source: 'error' }));
      
      // Network activity
      const network = this.networkActivity.get(effectiveTabId) || [];
      network.forEach(activity => allEvents.push({ ...activity, source: 'network' }));
      
      // WebSocket messages (get from page)
      if (this.pages.has(effectiveTabId)) {
        const page = this.pages.get(effectiveTabId);
        const wsMessages = await page.evaluate(() => window._wsMessages || []);
        wsMessages.forEach(msg => allEvents.push({ ...msg, source: 'websocket' }));
      }
      
      // Sort by timestamp
      allEvents.sort((a, b) => a.timestamp - b.timestamp);
      
      // Filter by since
      let filtered = since ? allEvents.filter(event => event.timestamp >= since) : allEvents;
      
      // Limit results
      filtered = filtered.slice(-limit);
    
      return {
        content: [{
          type: 'text',
          text: `All Debug Activity (${filtered.length} events):\n` + JSON.stringify(filtered, null, 2)
        }]
      };
    }
  • Tool registration in ListToolsRequestSchema response, including name, description, and input schema definition.
    {
      name: 'get_all_debug_activity',
      description: 'Get combined feed of all debug events',
      inputSchema: {
        type: 'object',
        properties: {
          tabId: { type: 'string' },
          since: { type: 'number' },
          limit: { type: 'number', default: 100 }
        }
      }
    },
  • Dispatcher case in CallToolRequestSchema handler that routes tool calls to the getAllDebugActivity method.
    case 'get_all_debug_activity':
      return await this.getAllDebugActivity(args);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a 'get' operation (implying read-only) and mentions 'combined feed' which suggests aggregation, but doesn't describe output format, pagination, rate limits, authentication needs, or whether it's destructive. For a tool with 3 parameters and no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the core purpose. Every word earns its place, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, no annotations, no output schema, multiple similar siblings), the description is incomplete. It doesn't explain what 'debug events' include, how parameters work, what the output looks like, or when to choose this over other debugging tools. For a tool in a crowded namespace with zero schema documentation, this provides insufficient context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. The description mentions 'combined feed' which relates to the output, but adds no meaning about the 3 input parameters (limit, since, tabId). It doesn't explain what 'limit' controls, what 'since' refers to (timestamp?), or how 'tabId' filters events. This fails to compensate for the schema coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get combined feed of all debug events' clearly states the action (get) and resource (debug events), but it's vague about what constitutes 'debug events' and doesn't distinguish this tool from sibling tools like get_console_logs, get_javascript_errors, or get_network_activity. It specifies 'combined feed' and 'all' which provides some scope, but lacks precision about what types of events are included.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like get_console_logs or get_network_activity. It mentions 'all debug events' which implies comprehensiveness, but doesn't specify contexts where this is preferred over more specific tools. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JediLuke/firefox-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server