Skip to main content
Glama

tab_press

Press a key or shortcut in the focused browser tab to close dialogs, move between fields, submit forms, or navigate lists, then return the updated screen content.

Instructions

Press a key or shortcut in the user's browser with the real keyboard, after bringing the tab to the front. It goes to whatever has focus there: Escape to close a dialog, Tab to move between fields, Enter to submit, arrows in a list. Returns what changed on screen, or the new screen after a navigation.

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

Input Schema

NameRequiredDescriptionDefault
keyYesKey name: Enter, Escape, Tab, Space, Backspace, Delete, ArrowUp/Down/Left/Right, Home, End, PageUp, PageDown, F1-F12, a letter or a digit.
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.
modifiersNoModifiers held for a shortcut: Meta (Command), Control, Alt (Option), Shift. E.g. ["Meta"] with "L".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the whole behavioral load; it does disclose two non-obvious traits: the tab is brought to the front first, and the key goes to whatever element currently has focus. It also states the return shape (what changed on screen, or the new screen after navigation). It says nothing about failure modes, invalid key names, or timing, so the disclosure is helpful but incomplete for a state-mutating input tool.

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?

Three sentences, front-loaded with the action and its context, followed by the concrete use cases and then the return value. The examples earn their space; only the return-value sentence could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description correctly supplies both the return value and the focus/bring-to-front behavior, which is enough for an agent to call it correctly. Gaps remain around error handling and whether the tool waits for effects to settle, which matter for a state-changing input tool.

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%, so all three parameters (key, tabId, modifiers) are already documented with the accepted key names and the default-tab behavior. The description's only added meaning is that the key lands on the focused element, which is a modest supplement rather than new parameter semantics; baseline 3 applies.

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 names a specific verb (press) and resource (a key/shortcut), plus the execution context: the user's browser with the real keyboard, scoped to the fronted tab. That browser scoping separates it from OS-level siblings like macos_keyboard_press without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Concrete when-to-use examples are supplied (Escape to close a dialog, Tab between fields, Enter to submit, arrows in a list), which tells an agent what this tool is for. There is no explicit when-not guidance or reference to a sibling like tab_type for entering text, so it stops short of full routing.

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