Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

press_key

Simulates pressing keyboard keys such as Enter, Tab, Escape, and arrow keys in a Chromium browser tab, optionally with modifier keys, to automate navigation and form interactions.

Instructions

Press a keyboard key (Enter, Tab, Escape, ArrowDown, etc.)

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": "press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey name (Enter, Tab, Escape, Backspace, ArrowUp, ArrowDown, etc.)
tabIdNoTab ID (optional)
modifiersNoModifier flags: 1=Alt, 2=Ctrl, 4=Meta/Cmd, 8=Shift

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and falls short. It does not say that the key goes to the focused element, whether keydown/keyup events fire, or that keys like Enter can submit forms and mutate page state (a potentially destructive side effect).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every word earns its place. It is perhaps too terse rather than too long, but structure itself is clean.

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 three-parameter input tool with a rich schema and no output schema, the definition covers the basics. However, with zero annotations it should mention focus targeting and the potentially state-changing effects of certain keys, which an agent needs before invoking it.

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 coverage is 100%, with key names and modifier bit flags fully documented in the schema, so the baseline is 3. The description only re-lists key examples already present in the schema's key field and adds no meaning about tabId targeting or modifier semantics.

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?

States a specific verb+resource ("Press a keyboard key") and gives concrete key examples, so the agent knows exactly what it does. It does not differentiate from siblings like fill or click, which also drive input into the focused element.

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 when-to-use guidance is given: nothing says the key is sent to the currently focused element, or when to prefer press_key over fill/click (e.g., Enter to submit, Tab to move focus). The key examples imply usage but do not state it.

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