Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

browser_snapshot

Capture a snapshot of the current browser state for use in automation workflows.

Instructions

browser snapshot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler for browser_snapshot. Uses Playwright's page.accessibility.snapshot() to capture the accessibility tree of the current page and returns it along with URL and title.
    async function browserSnapshot() {
      try {
        const page = await getPage();
        
        // Get accessibility tree
        const snapshot = await page.accessibility.snapshot();
    
        return {
          success: true,
          message: 'Accessibility snapshot captured',
          snapshot,
          url: page.url(),
          title: await page.title()
        };
    
      } catch (error) {
        logger.error(`Error getting snapshot: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Registration of browser_snapshot as a tool in the MCP tools/list response, alongside other browser extras. No input schema required.
    const browserExtras = [
      { n:'browser_navigate_back' }, { n:'browser_navigate_forward' }, { n:'browser_hover' }, { n:'browser_drag' },
      { n:'browser_select_option' }, { n:'browser_press_key' }, { n:'browser_snapshot' }, { n:'browser_console_messages' },
      { n:'browser_network_requests' }, { n:'browser_tab_list' }, { n:'browser_tab_new' }, { n:'browser_tab_select' },
      { n:'browser_tab_close' }, { n:'browser_file_upload' }, { n:'browser_wait' }, { n:'browser_wait_for' },
      { n:'browser_resize' }, { n:'browser_handle_dialog' }
    ];
    for (const b of browserExtras) {
      tools.push({ name: b.n, description: b.n.replace(/_/g,' '), inputSchema: { type:'object', properties:{} } });
    }
  • Dispatch routing: when tool 'browser_snapshot' is called, it calls browserTools.browserSnapshot() with no arguments.
    case 'browser_snapshot': data = await browserTools.browserSnapshot(); break;
  • Export of browserSnapshot function from browser_tools.js for use by server.js and other consumers.
      // Capture
      browserTakeScreenshot,
      browserSnapshot,
      browserPdfSave,
      
      // Tab management
      browserTabList,
      browserTabNew,
      browserTabSelect,
      browserTabClose,
      
      // Utilities
      browserConsoleMessages,
      browserFileUpload,
      browserWait,
      browserWaitFor,
      browserResize,
      browserHandleDialog,
      browserClose,
      browserInstall,
      browserNetworkRequests
    };
  • Example generation script: provides empty arguments for browser_snapshot tool.
    case 'browser_snapshot': return {};
Behavior1/5

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

Without annotations, the description should disclose behavioral traits such as side effects, permissions, or output nature. The current text offers none, leaving the agent completely uninformed about what invoking this tool entails.

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

Conciseness2/5

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

While the description is extremely short, it is under-specified rather than concise. The two words do not form a meaningful sentence and fail to earn their place by providing any actionable information.

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

Completeness1/5

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

Given the absence of annotations, output schema, and any meaningful description, the definition is completely inadequate for understanding the tool's functionality in context.

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

Parameters3/5

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

The tool has no parameters, and schema coverage is 100%. According to guidelines, baseline is 3 when coverage is high. The description adds no additional meaning, but the lack of parameters means no compensation is needed.

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

Purpose1/5

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

The description 'browser snapshot' is a tautology, simply restating the tool name without any verb or resource. It does not clarify what action the tool performs or how it differs from siblings like browser_navigate or browser_click.

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

Usage Guidelines1/5

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

No guidance is provided on when or why to use this tool. An AI agent cannot determine if snapshot captures a screenshot, DOM state, or something else, and has no hints about alternatives.

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/FutureAtoms/agentic-control-framework'

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