Skip to main content
Glama
JustasMonkev

MCP Accessibility Scanner

browser_navigate_back

Read-only

Return to the previous page in automated accessibility scans to ensure WCAG compliance verification during web navigation testing with MCP Accessibility Scanner.

Instructions

Go back to the previous page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that performs the browser back navigation using tab.page.goBack(), includes snapshot in response, and adds corresponding code snippet.
    handle: async (tab, params, response) => {
      await tab.page.goBack();
      response.setIncludeSnapshot();
      response.addCode(`await page.goBack();`);
    },
  • Schema definition for the browser_navigate_back tool, specifying name, title, description, empty input schema, and readOnly type.
    schema: {
      name: 'browser_navigate_back',
      title: 'Go back',
      description: 'Go back to the previous page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • Exports the goBack tool (browser_navigate_back) as part of the default tool array for registration.
    export default [
      navigate,
      goBack,
    ];
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and scope. The description adds no behavioral traits beyond what annotations provide, such as navigation history constraints or browser state implications. No contradiction with annotations exists.

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 waste. It is front-loaded and appropriately sized for a simple navigation tool, making it easy to understand quickly.

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

Completeness4/5

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

For a simple tool with no parameters, rich annotations (readOnlyHint, destructiveHint, openWorldHint), and no output schema, the description is complete enough. It could benefit from mentioning browser context or history state, but it adequately covers the core functionality given the structured data.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description does not need to explain parameters, and it adds no extra parameter information, which is appropriate given the lack of inputs.

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

Purpose5/5

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

The description 'Go back to the previous page' clearly states the specific action (go back) and resource (previous page). It distinguishes from siblings like browser_navigate_forward (forward navigation) and browser_navigate (general navigation), making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context (when there is a previous page to return to), but does not explicitly state when not to use it or name alternatives. It provides clear context but lacks explicit exclusions or named sibling comparisons beyond what's inferred from the tool name.

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/JustasMonkev/mcp-accessibility-scanner'

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