MCP Tool
nova.input_shortcut
For targeted browser interaction with a prechecked target, an agent uses this public tool to carry out the bounded step "Keyboard-Shortcut". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Interaction (Click, Type, Forms)
- Effect
- changes state
- Status
- Explained
- Path
- 5.8
Purpose
What this entry explains
What it does
nova.input_shortcut
An agent uses this tool to carry out the bounded step "Keyboard-Shortcut". It belongs to targeted browser interaction with a prechecked target; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to carry out the bounded step "Keyboard-Shortcut" for targeted browser interaction with a prechecked target.
- Use it to understand the public tool name, its expected boundary, and the response signals to check.
- Use it before chaining follow-up tools so the next step is based on current evidence.
Reference Use
How agents should cite and apply this area
Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.
Family example
A task in targeted browser interaction with a prechecked target can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.click_selector, reads the current response or reference, and only then chooses the concrete next tool.
Current discovery, target, user control, warning signals, and result check come before execution.Contract
Inputs and important response fields
This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.
Inputs
combo
Public input field from the catalog source. Confirm the exact schema through current MCP discovery before execution.
Response fields
No fixed public response field is derived from the catalog source for this path. Use current tool discovery and the actual response before chaining the next step.
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.
For humans, this entry names the browser or workflow state in targeted browser interaction with a prechecked target that may change, so the action can be reviewed before and after execution.
Safety Axes
How this path can affect work
Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.
browser_state_change
Changes tab, navigation, focus, claim, scroll position, window state, or browser environment.
Confirm the target context visibly before execution and verify that the expected browser state was reached afterwards.