Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

navigate

Automate web page navigation by directing browsers to specified URLs with options to wait for full page loads, powered by AutoProbeMCP's browser automation framework.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to
waitForLoadNoWait for page to fully load

Implementation Reference

  • The main handler for the 'navigate' tool. Parses input arguments using NavigateSchema, checks if a page is available, navigates to the specified URL (with optional wait for network idle), retrieves the page title, and returns a text response with the URL and title.
    case 'navigate': {
      if (!currentPage) {
        throw new Error('No browser page available. Launch a browser first.');
      }
    
      const params = NavigateSchema.parse(args);
      
      if (params.waitForLoad) {
        await currentPage.goto(params.url, { waitUntil: 'networkidle' });
      } else {
        await currentPage.goto(params.url);
      }
    
      const title = await currentPage.title();
      
      return {
        content: [
          {
            type: 'text',
            text: `Navigated to ${params.url}\nPage title: ${title}`
          }
        ]
      };
    }
  • Zod schema defining the input parameters for the 'navigate' tool: required URL (validated as string URL) and optional waitForLoad boolean (defaults to true). Used for input validation in the handler.
    const NavigateSchema = z.object({
      url: z.string().url(),
      waitForLoad: z.boolean().default(true)
    });
  • src/index.ts:158-176 (registration)
    Registration of the 'navigate' tool in the ListTools response, specifying name, description, and input schema matching the NavigateSchema.
    {
      name: 'navigate',
      description: 'Navigate to a URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'URL to navigate to'
          },
          waitForLoad: {
            type: 'boolean',
            default: true,
            description: 'Wait for page to fully load'
          }
        },
        required: ['url']
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't describe what 'navigate' entails—e.g., whether it opens a new tab, follows redirects, handles errors, or requires authentication. For a tool with potential side effects (like loading a webpage), this lack of detail is a significant gap.

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 front-loaded with the core action ('Navigate to a URL'), making it immediately scannable. Every word earns its place, and there's no redundancy or unnecessary elaboration.

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 (a navigation tool with potential behavioral nuances), lack of annotations, and no output schema, the description is incomplete. It doesn't cover what happens on success/failure, return values, or error handling. For a tool that interacts with external resources (URLs), more context is needed to guide the agent effectively.

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 schema description coverage is 100%, with clear descriptions for both parameters ('url' and 'waitForLoad'). The description adds no additional meaning beyond what the schema provides, such as URL format requirements or what 'fully load' means. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't enhance parameter understanding.

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

Purpose4/5

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

The description clearly states the action ('navigate') and target resource ('URL'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like 'click_element' or 'scroll' by focusing on URL navigation. However, it doesn't specify whether this is browser navigation or general URL access, which could be clarified.

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. It doesn't mention prerequisites (e.g., requiring a launched browser), exclusions (e.g., not for file URLs), or relationships with siblings like 'launch_browser' (which likely must precede it). Without this context, the agent must infer usage from tool names alone.

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/Wladastic/AutoProbeMCP'

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