Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

navigate

Opens a web page by navigating to a specified URL. Optionally waits for the page to fully load, ensuring content is ready for subsequent automation tasks.

Instructions

Navigate to a URL

Input Schema

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

Implementation Reference

  • Zod schema for the 'navigate' tool input: requires a valid URL string, with an optional boolean 'waitForLoad' that defaults to true.
    const NavigateSchema = z.object({
      url: z.string().url(),
      waitForLoad: z.boolean().default(true)
    });
  • src/index.ts:158-176 (registration)
    Tool registration entry for 'navigate' in the ListToolsRequestSchema handler, defining name, description, and inputSchema (url string required, waitForLoad boolean optional with default true).
    {
      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']
      }
    },
  • Handler implementation for the 'navigate' tool: checks if a browser page is available, parses args with NavigateSchema, navigates to URL via Playwright's page.goto() (using 'networkidle' if waitForLoad is true), retrieves the page title, and returns a success message 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}`
          }
        ]
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral traits. It only states 'Navigate to a URL' without disclosing effects on browser state, handling of special URLs, or potential side effects like navigation history changes.

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 without fluff. It is front-loaded and concise, though it could be slightly expanded for more context without losing brevity.

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 that there is no output schema and only two simple parameters, the description still lacks important context such as return behavior, error states, behavior when waitForLoad is false, or prerequisites like needing an active browser session.

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?

Schema description coverage is 100%, so the schema already adequately documents both parameters. The description adds no additional meaning beyond what is in the schema.

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 clearly states the action (Navigate) and the resource (a URL). It is concise and effectively distinguishes the tool from siblings like click_element or type_text, which perform different actions.

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 guidance on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or when not to use navigate (e.g., when a page is already loaded).

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

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