Skip to main content
Glama

woolworths_navigate

Navigate directly to specific Woolworths website pages to access products, specials, or shopping features using provided URLs.

Instructions

Navigate to a specific URL on the Woolworths website

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The function that executes the tool logic for woolworths_navigate, navigating the current browser page to the specified URL and returning the new URL and title.
    async function handleNavigate(args: any): Promise<any> {
      if (!browser || !currentPage) {
        throw new Error("Browser is not open. Use woolworths_open_browser first.");
      }
    
      await currentPage.goto(args.url, { waitUntil: "networkidle2" });
    
      return {
        success: true,
        url: currentPage.url(),
        title: await currentPage.title(),
      };
    }
  • The tool definition including name, description, and input schema for woolworths_navigate.
    {
      name: "woolworths_navigate",
      description: "Navigate to a specific URL on the Woolworths website",
      inputSchema: {
        type: "object",
        properties: {
          url: {
            type: "string",
            description: "The URL to navigate to",
          },
        },
        required: ["url"],
      },
    },
  • src/index.ts:627-629 (registration)
    The switch case that registers and dispatches calls to the woolworths_navigate handler in the tool call request handler.
    case "woolworths_navigate":
      result = await handleNavigate(args || {});
      break;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal insight. It states the action but doesn't describe what 'navigate' entails (e.g., page loading, potential errors, session persistence, or interaction with other tools). For a navigation tool in a web automation context, this lack of detail on behavior 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, direct sentence that efficiently conveys the core action without unnecessary words. It is front-loaded with the key verb and resource, making it easy to parse quickly, which is ideal for conciseness in a tool definition.

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 of web navigation (which can involve errors, loading states, or session dependencies) and the absence of both annotations and an output schema, the description is incomplete. It doesn't address what happens after navigation (e.g., success indicators, returned page content, or error handling), leaving critical context gaps for the agent.

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 input schema has 100% description coverage, with the 'url' parameter clearly documented. The description adds no additional meaning beyond what the schema provides (e.g., no constraints on URL format or domain specificity). According to the rules, with high schema coverage, the baseline is 3 even without param info in the description.

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 to') and target resource ('a specific URL on the Woolworths website'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'woolworths_open_browser' or 'woolworths_get_categories' that might involve navigation implicitly, which prevents a perfect score.

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., whether the browser must be open first using 'woolworths_open_browser'), nor does it clarify use cases like navigating to product pages versus category pages, leaving the agent to infer context from sibling 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

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/elijah-g/Woolworths-mcp'

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