Skip to main content
Glama
Sign In
real-browser-mcp-server

real-browser-mcp-server

by codeiva11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

press_key

Press keyboard keys with configurable modifiers, repeat counts, and keystroke delays to automate form navigation, shortcuts, and repeated input in browser tasks.

Instructions

Press keyboard keys with configurable modifier keys, repeat count, and keystroke delay.

Input Schema

NameRequiredDescriptionDefault
keyYesKey name (e.g. Enter, Tab, ArrowDown, a)
countNoNumber of times to press the key
modifiersNoModifier keys (Alt, Control, Meta, Shift)
humanDelayNoAdd natural delay between repeated presses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.3.14
    • addedInput schema / properties / count / maximum
      Added value: +100
  2. First observedv3.2.13

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden yet discloses nothing about focus requirements, which element receives the key event, error behavior for invalid key names, or side effects. It only restates the configurable parameters rather than describing how the tool behaves.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately sized, though the space saved is space not used for the missing behavioral context.

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?

For a simple four-parameter tool with fully documented schema and no output schema, the description covers the basic operation. However, with annotations absent, it should at least state that keys are sent to the currently focused element/session, which is the main thing an agent could get wrong.

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 every parameter is already documented in the schema with examples and defaults. The description merely echoes 'modifier keys, repeat count, and keystroke delay' without adding format or interaction details, so the baseline 3 applies.

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 states a specific verb (press) and resource (keyboard keys) plus the configurable axes, which is clear. It does not distinguish itself from siblings like `type` or `click`, so an agent must infer that this is for discrete key presses rather than text entry.

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?

There is no guidance on when to use this tool versus `type` (text entry) or `click`, nor any mention of prerequisites such as an initialized browser session or a focused element. The agent is left to infer all selection criteria.

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