chatgpt-remote-browser-mcp

Press key in shared browser tab

press

Send a keyboard key press to the active shared browser tab to trigger actions or modify page state.

Instructions

Press a keyboard key in a currently shared tab. This can change browser or external-site state.

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": {
      "handle": "<handle>",
      "key": "<key>"
    },
    "name": "press"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`handle`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Sep 8, 2026

TDQS

B3.4/5.0

Behavior4/5

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

The description discloses that pressing a key can change browser or external-site state, which goes beyond the annotations (readOnlyHint=false, destructiveHint=false). It also implies a precondition that the tab must be currently shared, offering useful behavioral context.

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 concise and well-structured, with two short sentences that convey the essential action and side effect without unnecessary detail. It is efficient and easy to parse.

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?

The description is adequate for a simple tool with no output schema, but it lacks usage guidance and parameter context. It mentions the shared-tab prerequisite and potential state changes, but does not explain how the handle identifies the tab or what keys are accepted, leaving some gaps for an agent.

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

Parameters1/5

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

The description does not mention the parameters 'handle' or 'key' at all, providing no insight into what values they expect or how they relate to the action. Since schema coverage is 0% and the description does not compensate, parameter semantics are completely lacking.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (press a keyboard key) and the target (a currently shared tab). It also distinguishes from sibling tools like type, click, and scroll by specifying 'keyboard key' and 'currently shared tab', making the purpose unambiguous.

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 provides no guidance on when to use this tool over alternatives such as type or click. It neither explains the difference between pressing a single key and entering text, nor mentions any prerequisites beyond the tab being shared, leaving the agent to infer usage context.

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

Deploy Server