Skip to main content
Glama
Sign In
agent-browser

agent-browser

by EgiStr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

press_key

Sends keyboard key presses, such as Enter, Escape, or Control+A, to the active browser tab to trigger navigation, form submission, or shortcuts.

Instructions

Press a key in the agent tab, e.g. Enter, Escape, PageDown, 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": "press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so the description carries the full burden. It only says the key is pressed "in the agent tab"; it does not disclose focus requirements, whether the key goes to the active element, whether the call blocks, or what happens if the key name is invalid.

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

Conciseness5/5

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

One short sentence, front-loaded with the action and enriched with examples. Nothing extraneous.

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?

An output schema exists so return values need not be explained, and there is only one parameter. However, for a browser-automation tool, the missing focus/target semantics leave a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: the examples (Enter, Escape, PageDown, Control+A) reveal the accepted key-name vocabulary and the modifier-chord syntax, which the bare 'key' string schema does not.

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 ("Press a key in the agent tab") and lists concrete examples of keys. It implicitly distinguishes itself from type_text and click by being about single key presses, though it never names those siblings.

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 this versus type_text (for text entry) or click, nor any precondition such as needing an element focused first. The agent must infer usage from the description alone.

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