dawg-mcp

Overview Schema Source Related Servers Discussions Admin

browser_press_key

Send keyboard key presses to a remote browser, supporting single keys and shortcuts like Control+a. Ideal for automating browser navigation and forms.

Instructions

Press a keyboard key (e.g. "Enter", "Escape", "ArrowDown", "Control+a").

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

Name	Required	Description	Default
`key`	Yes
`session_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided; description only says 'Press' without detailing side effects (e.g., whether it affects focus, fires events, or requires active session). Modifier key example 'Control+a' suggests combination press, but no clarification.

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?

Single sentence with examples; no redundant words. Could be improved by adding a note about parameter details, but current form is efficient.

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?

Tool is simple with only 2 parameters and no output schema, so minimal description may suffice, but lacks context on how it interacts with the browser (e.g., active tab, focused element). Somewhat incomplete.

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?

Schema description coverage is 0%; the description does not explain the key parameter's allowed values (e.g., case sensitivity, special key names) or the session_id parameter's purpose. Examples only hint at valid entries.

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?

Clear verb-resource combination: 'Press a keyboard key'. Examples differentiate from sibling tool 'browser_type' which types text strings, and 'browser_click' which clicks mouse buttons.

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?

No guidance on when to use press_key versus similar tools like browser_type or browser_fill_form. No mention of prerequisites (e.g., element focus) or fallback tools.

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