Skip to main content
Glama
Sign In
BrowserPilot

BrowserPilot

by soulxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_press_key

Press keyboard keys like Enter, Escape, or Tab to interact with web pages, enabling natural language browser automation for testing and data scraping.

Instructions

Press keyboard key

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "browser_press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey to press (e.g., Enter, Escape, Tab)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
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 and states only the literal action. It fails to disclose that pressing a key can trigger side effects (e.g., Enter submitting forms, Escape closing dialogs), whether the event targets the focused element, or what the tool returns.

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 four-word description has zero wasted words and is appropriately sized for a single-parameter tool. Every word earns its place.

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?

Despite being a simple one-parameter tool, the description omits selection-critical context: when to choose this over browser_type, whether the key activates the focused element or the page, and what observable effects to expect after the press. The large 16-tool sibling set increases the risk of confusion.

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?

Schema description coverage is 100% — the key parameter is already documented with examples (Enter, Escape, Tab). The description adds nothing beyond what the schema provides, so the baseline of 3 applies.

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 states a clear verb and resource ('Press keyboard key'), which identifies the core action unambiguously. However, it does not differentiate from siblings like browser_type (text input) or browser_click, leaving the distinction between pressing a key and typing text implicit.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that browser_type is for entering text, whether the press targets the focused element, or whether this is appropriate for shortcuts and navigation keys.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools