Skip to main content
Glama
Sign In
omni-browser

omni-browser

by rianprei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_press

Press a specified key on a focused element selected by CSS selector to simulate keyboard input in browser automation workflows.

Instructions

Press a key in a focused element.

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": {
      "selector": "<selector>",
      "key": "<key>"
    },
    "name": "browser_press"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations, so the description carries the full burden and delivers very little. It doesn't say whether the selector receives focus before the key is pressed, what keyboard events are dispatched, or whether trusted events reach the page.

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?

A single short sentence with no wasted words, but it is under-specified rather than concise. There's no structure for key format, targeting behavior, or examples.

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?

With no annotations, no output schema, and zero schema coverage on both parameters, the description should explain targeting and key syntax but instead leaves both unaddressed. An agent cannot reliably call this tool from the definition alone.

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% for two required parameters, and the description adds no meaning: 'key' format (e.g., 'Enter' vs 'Control+A') and 'selector' syntax are both undocumented. Worse, 'in a focused element' muddies what the selector is for rather than clarifying it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (press) and resource (a key), which distinguishes it from browser_click or browser_fill. But the phrase 'in a focused element' is vague and doesn't tell an agent whether the tool targets the selector or the currently focused element, leaving genuine ambiguity.

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 indication of when to use this instead of siblings like browser_fill, browser_click, or browser_select, and no prerequisites such as focusing an element first. The agent must infer usage entirely.

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