Skip to main content
Glama

pilot_type

Type text character by character into focused web elements for automated browser interactions.

Instructions

Type text into the currently focused element (character by character).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to type
submitNoPress Enter after typing

Implementation Reference

  • Implementation of the pilot_type tool handler in src/tools/interaction.ts.
    server.tool(
      'pilot_type',
      'Type text into the currently focused element (character by character).',
      {
        text: z.string().describe('Text to type'),
        submit: z.boolean().optional().describe('Press Enter after typing'),
      },
      async ({ text, submit }) => {
        await bm.ensureBrowser();
        try {
          const page = bm.getPage();
          await page.keyboard.type(text);
          if (submit) await page.keyboard.press('Enter');
          bm.resetFailures();
          return { content: [{ type: 'text' as const, text: `Typed ${text.length} characters${submit ? ' + Enter' : ''}` }] };
        } catch (err) {
          bm.incrementFailures();
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully communicates the key behavioral trait of character-by-character input (important for triggering JavaScript keyboard events), but lacks critical mutation context: it does not state whether existing text is cleared or appended to, what happens if the element isn't focused, or rate-limiting/speed characteristics.

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?

Extremely efficient at 11 words. Every element earns its place: the parenthetical '(character by character)' is critical behavioral information that distinguishes this tool. No redundant or filler text present.

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 2-parameter mutation tool without output schema or annotations, the description covers the basic operation but has gaps in workflow context. It does not explain the focusing prerequisite (though 'currently focused' implies it), side effects on existing text, or return behavior, which are necessary for safe autonomous execution.

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?

With 100% schema description coverage ('Text to type', 'Press Enter after typing'), the baseline score is 3. The description adds no specific parameter guidance beyond the schema (e.g., text format constraints, submit behavior details), but does not need to given the comprehensive schema.

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 provides a specific verb ('Type'), target resource ('currently focused element'), and crucial behavioral differentiator ('character by character') that distinguishes it from the sibling 'pilot_fill' tool. However, it does not explicitly name the sibling alternative to provide clear selection guidance.

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

Usage Guidelines3/5

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

The 'character by character' phrase implies this is for simulating human typing rather than instant value insertion, giving implied usage context. However, there are no explicit guidelines on when to prefer this over 'pilot_fill', no mention of prerequisites (e.g., requiring a focused element via pilot_click first), and no error conditions described.

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