Skip to main content
Glama
Sign In
Hive Web

Hive Web

by YegorMy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

action_web_press

Press a keyboard key in a live browser session to simulate user input such as Enter, Escape, or ArrowDown for web automation.

Instructions

Press a keyboard key in the live browser session, e.g. Enter, Escape, ArrowDown.

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": {
      "session_id": "<session_id>",
      "key": "<key>"
    },
    "name": "action_web_press"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
session_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The description is straightforward for a simple key press action, but lacks details on behavior such as whether key release is automatic or if special key combinations are supported. No annotations exist to supplement.

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 very concise, using a single sentence that front-loads the action and examples, but it borders on under-specification.

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 two-parameter tool with no annotations, the description is minimally adequate but lacks important context about key value formats and the necessity of session_id, limiting its completeness.

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?

With 0% schema description coverage, the description provides no information about the parameters (key and session_id), leaving the agent without guidance on valid key values or the role of session_id.

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?

The description clearly states the tool presses a keyboard key and provides specific examples (Enter, Escape, ArrowDown), distinguishing it from sibling tools like action_web_click and action_web_type.

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?

The description implies usage for pressing single keys but does not explicitly state when to use this tool versus alternatives like action_web_type for text input or action_web_click for mouse actions.

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