Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

press_key

Simulates keyboard key presses such as Enter, Escape, Tab, ArrowDown, and Backspace in a controlled browser tab to trigger form submissions, navigation, and focus changes.

Instructions

Press a keyboard key (e.g. Enter, Escape, Tab, ArrowDown, Backspace)

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
keyYes
tabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does not explain whether the key is sent to the active element, whether the browser page must be focused, how tabId affects dispatch, or what happens if the key name is invalid.

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 description is a single front-loaded sentence with no filler. The examples are compact and directly useful, so every part 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?

For an action tool with no annotations, no output schema, and 0% schema description coverage, the definition is too thin. It omits essential operational details such as focus requirements, tab targeting, and key-name conventions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only helps with the 'key' parameter through examples. It says nothing about the 'tabId' parameter, including whether it selects the target tab or defaults to the active tab.

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 uses a specific verb and resource: 'Press a keyboard key,' and gives concrete examples such as Enter, Escape, and ArrowDown. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling 'type' tool.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as type, fill, or click. The key examples imply keyboard-interaction use cases, but there is no stated condition, exclusion, or prerequisite.

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