Skip to main content
Glama

pilot_frame_reset

Switch back to the main browser frame after interacting with iframes to continue automation tasks.

Instructions

Switch back to the main frame. Use after interacting with an iframe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for pilot_frame_reset, which calls bm.resetFrame().
    server.tool(
      'pilot_frame_reset',
      'Switch back to the main frame. Use after interacting with an iframe.',
      {},
      async () => {
        await bm.ensureBrowser();
        bm.resetFrame();
        return { content: [{ type: 'text' as const, text: 'Switched to main frame. Refs cleared — run pilot_snapshot for fresh refs.' }] };
      }
    );
  • Registration point for iframe tools, including pilot_frame_reset.
      'pilot_frames', 'pilot_frame_select', 'pilot_frame_reset',
    ]);
Behavior3/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. It explains the state change (switching frames) but omits idempotency details (what happens if already on main frame), error conditions, or side effects on iframe 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?

Two sentences with zero waste: first establishes the action, second provides essential workflow context. Front-loaded structure places the operative verb immediately.

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

Completeness4/5

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

Appropriately complete for a simple context-switching tool with no output schema. Covers essential usage context, though mentioning error behavior when called outside iframe contexts would strengthen it further.

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?

Zero parameters present, establishing baseline 4 per rubric. No parameter semantics are needed or expected given the empty input 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 uses a specific verb ('Switch back') and resource ('the main frame'), clearly distinguishing it from sibling 'pilot_frame_select' by implying this returns to default context rather than selecting a specific frame.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit temporal guidance ('Use after interacting with an iframe') that establishes the workflow context. While it doesn't explicitly name 'pilot_frame_select' as the alternative or state negative conditions, the 'after interacting' clause effectively signals when this tool is needed.

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