Skip to main content
Glama

woolworths_close_browser

Close the browser session after completing Woolworths shopping tasks to free system resources and maintain browser performance.

Instructions

Closes the browser instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that closes the Puppeteer browser instance if it is open, clears references, and returns a success or error message.
    async function handleCloseBrowser(args: any): Promise<any> {
      if (!browser) {
        return {
          success: false,
          message: "Browser is not open.",
        };
      }
    
      await browser.close();
      browser = null;
      currentPage = null;
    
      return {
        success: true,
        message: "Browser closed. Session cookies have been preserved.",
      };
    }
  • Tool schema definition including name, description, and empty input schema (no parameters required). Part of the TOOLS array used for tool listing.
    {
      name: "woolworths_close_browser",
      description: "Closes the browser instance",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:635-637 (registration)
    Registration of the handler in the main switch statement that dispatches tool calls to the appropriate function.
    case "woolworths_close_browser":
      result = await handleCloseBrowser(args || {});
      break;
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 disclosure. 'Closes the browser instance' implies a destructive action that terminates a session, but it doesn't specify what happens to any open pages, cookies, or state. It also doesn't mention whether this requires an existing browser instance to be open or what happens if called multiple times.

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, clear sentence with no wasted words. It's perfectly front-loaded with the essential information and doesn't contain any unnecessary elaboration. This is an excellent example of conciseness for a simple operation.

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

Completeness3/5

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

For a zero-parameter tool with no output schema, the description adequately states what the tool does. However, as a potentially destructive operation with no annotations, it should ideally mention behavioral implications like what gets cleaned up or whether this affects other tools. The completeness is minimal but sufficient for the basic operation.

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?

The tool has zero parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't mention parameters since none exist, which is correct for this case. A baseline of 4 is appropriate for zero-parameter tools.

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 ('Closes') and the resource ('the browser instance'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools, but given the tool name 'close_browser' and sibling 'open_browser', the distinction is somewhat implied through naming conventions.

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 or what context it should be used in. While it might be obvious from the name that this is for closing a browser after other operations, there's no explicit mention of prerequisites, sequencing, or relationship to sibling tools like 'open_browser'.

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