Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Press key

press

Send keyboard keys like Enter, Escape, Tab, or Control+A to a browser page, optionally focusing a target element first so the key reaches the intended control.

Instructions

Press a keyboard key (Enter, Escape, Tab, ArrowDown, Control+A…). Optionally focus a target first.

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

Input Schema

NameRequiredDescriptionDefault
keyYesPlaywright key name, e.g. Enter or Control+A.
refNoElement ref from the latest snapshot, e.g. e12. Preferred over selectors.
confirmNoConfirm a high-impact action when the server policy is ask.
observeNoReturn a compact change observation after the action (default true).
selectorNoCSS selector (use when no ref is available).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The only annotation is readOnlyHint=false, so the description carries most of the behavioral disclosure burden for a mutating tool. It mentions that a target can optionally be focused first, which adds some context, but it does not explain what the 'confirm' parameter's ask-policy means in practice, what 'observe' returns by default, or what side effects pressing a key may trigger.

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?

The description is two short sentences with no wasted words, and the core action is front-loaded. The parenthetical key examples are useful but could have been left to the schema.

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 a five-parameter mutating tool with a confirm-policy parameter, an observe toggle defaulting to true, and no output schema, the description is thin. It omits how confirmation works and what observation output looks like, leaving the agent to rely entirely on the schema for operational behavior.

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 description coverage is 100%, so the schema already documents all five parameters. The description adds only the implicit link between 'focus a target first' and the ref/selector parameters, plus key examples that largely duplicate the schema's key description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 supplies concrete key examples (Enter, Escape, Control+A). It is clear what the tool does, but it does not differentiate itself from the sibling 'type' or 'fill' tools, which an agent could easily confuse with key pressing.

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

Usage Guidelines3/5

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

Usage is implied by the examples and the note about optionally focusing a target first, but there is no explicit statement of when to prefer this over 'type' or 'fill', or when not to use it. The agent must infer the distinction between pressing keys and typing text.

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

Deploy Server

Other Tools