Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

browser_navigate_back

Go to the previous page in the browser. Navigates back one step in the browsing history.

Instructions

browser navigate back

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The function that implements the 'browser_navigate_back' tool logic. It uses Puppeteer's page.goBack() to navigate to the previous page in history, waits for DOM content to load, and returns success/failure with the new page URL and title.
    /**
     * Go back to previous page
     */
    async function browserNavigateBack() {
      try {
        const page = await getPage();
        
        const response = await page.goBack({
          waitUntil: 'domcontentloaded',
          timeout: config.timeout
        });
    
        if (!response) {
          return {
            success: false,
            message: 'No previous page in history'
          };
        }
    
        return {
          success: true,
          message: 'Navigated back',
          url: page.url(),
          title: await page.title()
        };
    
      } catch (error) {
        logger.error(`Error navigating back: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Registration of 'browser_navigate_back' as a tool name in the MCP server's tools/list response. It's listed in the browserExtras array and added to the tools list with a generated description.
    // Add extended browser tool schemas to exceed 50 tools (matches prior capability set)
    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 of the 'browser_navigate_back' tool call in the tools/call handler. It invokes browserTools.browserNavigateBack() when the tool name matches.
    case 'browser_navigate_back': data = await browserTools.browserNavigateBack(); break;
  • Tool schema definition for 'browser_navigate_back'. The input schema is an empty object since this tool takes no arguments.
        { 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:{} } });
      }
      sendResponse(id, { tools });
      break;
    
    case 'tools/call':
    case 'tools/run': {
      const toolName = method === 'tools/call' ? params.name : params.tool;
      logger.info(`[tools] ${method} name=${toolName}`);
      const args = method === 'tools/call' ? (params.arguments || params.parameters || {}) : (params.args || {});
      let data;
      try {
        switch (toolName) {
          case 'setWorkspace':
Behavior1/5

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

No annotations provided. The description does not disclose any behavioral traits (e.g., effect on browser history, prerequisites, side effects). Adds no information beyond the name.

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?

Very concise but insufficiently informative. It is a tautology, not a proper description. The conciseness is wasted by not providing useful content.

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 no output schema, no annotations, and no parameters, the description must be complete. It fails to explain the tool's purpose or behavior, making it inadequate.

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?

The tool has no parameters, so schema coverage is 100% trivially. However, the description fails to add meaning; it does not explain what navigating back entails. Baseline for 0 params is 4, but this description is merely a label.

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 is 'browser navigate back', which merely restates the tool name. It is a tautology and provides no specific verb or resource beyond the name itself.

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 on when to use this tool versus siblings like browser_navigate or browser_navigate_forward. No context or alternatives 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

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