Skip to main content
Glama
nfodor

Chromium ARM64 Browser

by nfodor

run_debugger_mode

Debug application issues by activating debugger mode for web testing and automation on ARM64 devices.

Instructions

Run debugger mode to debug issues in the application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: ensures Chromium is running, evaluates JavaScript to gather debug info (URL, user agent, sizes, performance), parses it, and returns formatted text response.
    async runDebuggerMode() {
      await this.ensureChromium();
      
      const result = await this.sendCDPCommand('Runtime.evaluate', {
        expression: `
          JSON.stringify({
            url: window.location.href,
            userAgent: navigator.userAgent,
            screenSize: \`\${screen.width}x\${screen.height}\`,
            viewportSize: \`\${window.innerWidth}x\${window.innerHeight}\`,
            performance: {
              memory: performance.memory ? {
                used: Math.round(performance.memory.usedJSHeapSize / 1024 / 1024) + 'MB',
                total: Math.round(performance.memory.totalJSHeapSize / 1024 / 1024) + 'MB'
              } : 'Not available',
              timing: performance.timing ? {
                pageLoad: performance.timing.loadEventEnd - performance.timing.navigationStart + 'ms',
                domReady: performance.timing.domContentLoadedEventEnd - performance.timing.navigationStart + 'ms'
              } : 'Not available'
            }
          });
        `,
        returnByValue: true
      });
      
      const debugInfo = JSON.parse(result.result?.value || '{}');
      
      return {
        content: [{ type: 'text', text: `Debugger Mode Results:\\n${JSON.stringify(debugInfo, null, 2)}` }],
      };
    }
  • index.js:319-326 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the tool name, description, and empty input schema.
    {
      name: 'run_debugger_mode',
      description: 'Run debugger mode to debug issues in the application',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • index.js:389-390 (registration)
    Switch case in CallToolRequestSchema handler that dispatches calls to the runDebuggerMode method.
    case 'run_debugger_mode':
      return await this.runDebuggerMode();
  • Input schema definition for the tool: empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
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 the tool runs debugger mode but doesn't explain what that entails—e.g., whether it's interactive, what data it collects, if it modifies the application state, or how results are presented. This is a significant gap for a tool with potential behavioral complexity.

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

Conciseness4/5

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

The description is a single, efficient sentence that states the purpose without unnecessary words. It's front-loaded and to the point, though it could be slightly more specific to improve clarity without adding bulk.

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 complexity implied by 'debugger mode', lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool does behaviorally, what output to expect, or how it differs from sibling tools, leaving gaps for effective agent use.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description appropriately doesn't discuss parameters, avoiding redundancy.

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 states the tool's purpose as 'run debugger mode to debug issues in the application', which includes a verb ('run') and resource ('debugger mode') with a goal ('debug issues'). However, it's somewhat vague about what 'debugger mode' entails compared to sibling tools like 'run_audit_mode' or 'run_performance_audit', lacking specific differentiation in scope or method.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description mentions debugging issues but doesn't specify what types of issues, prerequisites, or when to choose this over other debugging-related siblings like 'get_console_errors' or 'evaluate'. This leaves usage context implied at best.

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

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/nfodor/mcp-chromium-arm64'

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