veilbrowser

veil_press

Press a specified key (e.g., Enter, Tab, Escape) on the currently focused element to submit forms, navigate fields, or trigger actions.

Instructions

Press a single named key on the focused element. Use 'Enter' to submit a search box or form (fill a field, then veil_press Enter). Supported: Enter, Tab, Escape, Backspace, Delete, ArrowUp, ArrowDown, ArrowLeft, ArrowRight, Home, End, PageUp, PageDown.

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

Input Schema

Name	Required	Description	Default
`key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It lists supported keys and mentions pressing on the focused element. But it omits details like behavior when no element is focused, whether it waits, or side effects like form submission (only implied). Adequate but not rich.

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?

Two concise sentences, first states purpose, second provides usage example and supported keys. No redundant information; efficiently front-loaded.

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?

Given a simple tool with one parameter and no output schema or annotations, the description covers the basic action and supported keys. However, it lacks info on prerequisites (element must be focused), return value, or error handling. Adequate but not fully comprehensive.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate. It repeats the enum list from the schema (Enter, Tab, etc.) but adds no extra semantics like case sensitivity or special usage. Minimal value beyond the schema.

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's action ('press a single named key') and the target ('focused element'). It is specific and distinguishable from sibling tools like veil_type (typing strings) and veil_click (clicking).

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

Usage Guidelines4/5

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

The description provides a concrete use case: 'Use Enter to submit a search box or form (fill a field, then veil_press Enter).' This gives clear context. However, it does not explicitly state when not to use this tool or compare to alternatives like veil_type for text entry.

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