Skip to main content
Glama

Press key

browser_press_key

Simulates pressing a keyboard key, such as Enter, Escape, Tab, or Control+A, in a live Chrome session to trigger actions or navigate forms.

Instructions

Press a keyboard key, e.g. Enter, Escape, ArrowDown, Tab, Control+A, Meta+K.

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 name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about where the key event is dispatched (focused element vs. page body), whether modifier chords are actually supported, or what happens if no element is focused. Only the key-name examples hint at capability, leaving the core behavior undisclosed.

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?

A single front-loaded sentence with the purpose first and examples second; nothing is wasted and no padding surrounds it.

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?

It is a simple one-parameter tool with full schema coverage and no output schema, so little is strictly required. Still, for a browser automation primitive the omission of focus/context requirements and result behavior leaves a meaningful gap for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns more by demonstrating naming conventions the bare schema ('Key name') does not: named keys like ArrowDown and chord syntax like 'Control+A' and 'Meta+K'. That directly tells an agent how to format the argument.

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 gives a specific verb and resource ('Press a keyboard key') and clarifies the resource with concrete key examples. It is immediately clear this is keyboard input rather than mouse or navigation, though it never explicitly contrasts itself with siblings like browser_type.

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?

There is no guidance on when to choose this over browser_type (text entry) or browser_click, nor any precondition such as needing an element focused first. The agent must infer the use case entirely from the one-line purpose.

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