Skip to main content
Glama

pilot_reload

Reload the current web page in the browser automation session to refresh content or resolve loading issues.

Instructions

Reload the current page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the pilot_reload tool handler.
    server.tool(
      'pilot_reload',
      'Reload the current page.',
      {},
      async () => {
        await bm.ensureBrowser();
        try {
          const page = bm.getPage();
          await page.reload({ waitUntil: 'domcontentloaded', timeout: 15000 });
          bm.resetFailures();
          return { content: [{ type: 'text' as const, text: `Reloaded ${page.url()}` }] };
        } catch (err) {
          bm.incrementFailures();
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
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 fails to mention critical side effects: potential loss of unsaved form data, whether this performs a hard or soft cache refresh, or implications on network requests and page state.

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 three-word description is maximally concise with zero redundancy, front-loading the critical action information. Every word earns its place despite the brevity, though additional behavioral detail would have been warranted.

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?

Given the browser automation context (evident from 40+ sibling tools) and the state-mutating nature of page reloads, the description is minimally viable but incomplete. It lacks necessary context about whether form data persists, cache behavior, or output indicators, which are critical given the absence of an output schema or annotations.

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 input schema contains zero properties with 100% coverage (empty object), establishing the baseline score of 4. The description appropriately requires no additional parameter elaboration given the absence of configurable inputs.

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 identifies the specific action (reload) and target (current page), providing a specific verb-resource mapping. However, it lacks explicit differentiation from sibling navigation tools like pilot_navigate (which navigates to new URLs) or pilot_back/forward (history navigation).

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 (e.g., pilot_navigate), prerequisites (such as having an active page), or specific conditions warranting a reload (e.g., stale content, refreshing form state).

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/TacosyHorchata/Pilot'

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