Skip to main content
Glama

Browser Keyboard

browser_keyboard

Send keyboard input to SAP GUI sessions to press keys or type text character by character for navigation and field entry during UI automation.

Instructions

Send keyboard input (key press or text typing). Important: For SAP shortcuts like Ctrl+S, prefer sap_press_key which auto-reads the status bar! For filling multiple form fields, use sap_fill_form - much faster. Args: key = key to press (e.g., 'Enter', 'Tab', 'F3'), text = text to type character by character.

Session parameter:

  • session=None (default): Uses primary session ("s1")

  • session="s2": Targets specific session (for parallel agents)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_keyboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoKey to press (e.g., 'Enter', 'Tab', 'F3').
textNoText to type character by character.
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.

Output Schema

NameRequiredDescriptionDefault
keyNoKey pressed
textNoText typed
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully explains that text is typed character by character and that session='s2' exists for parallel agents, but it omits where the input goes (focused element?), whether an element must be focused first, and what happens if typing fails or the target lacks focus.

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

Conciseness3/5

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

The opening sentence and the sibling alternatives are well front-loaded, but the 'Args:' list and the 'Session parameter' block largely restate schema descriptions, adding redundant bulk that does not earn its place.

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?

An output schema exists, so return values need no explanation, and the description covers the confusing parts: key vs text, session targeting, and preferred alternatives. What remains missing is focus/precondition behavior for a browser input tool, a modest gap.

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 the schema already documents all four parameters. The 'Args:' block repeats those descriptions almost verbatim and adds only example key names ('Enter', 'Tab', 'F3'), so the description adds little beyond the structured fields.

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 and resource: 'Send keyboard input (key press or text typing)'. It also distinguishes itself from two named siblings (sap_press_key, sap_fill_form), though it never clarifies how it relates to the closer generic sibling browser_fill, which likely also types text.

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?

Gives explicit routing guidance: use sap_press_key for SAP shortcuts like Ctrl+S, and sap_fill_form for multiple form fields. It does not say when to choose key vs text mode, nor when browser_fill would be preferable, so one meaningful alternative is left unaddressed.

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