MCP Tool
nova.tools_bundle
For browser environment, window state, and isolated execution surfaces, an agent uses this public tool to check the state or evidence for "Device-Emulation Bundle". It explains which current signal can be used as evidence and when a follow-up step needs a fresh target check.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Device Emulation
- Effect
- read-only
- Status
- Explained
- Path
- 21.5
Purpose
What this entry explains
What it does
nova.tools_bundle
An agent uses this tool to check the state or evidence for "Device-Emulation Bundle". It belongs to browser environment, window state, and isolated execution surfaces; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to check the state or evidence for "Device-Emulation Bundle" for browser environment, window state, and isolated execution surfaces.
- 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 touches data, identity, or permissions in browser environment, window state, and isolated execution surfaces that may be used only with clear purpose.
The agent starts with nova.emulation_set_device_metrics, reads the current response or reference, and only then chooses the concrete next tool.
Sensitive values stay in current scope; they are not guessed, logged, or copied into other contexts.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
bundle
Tool-bundle name. Use discovery to see available tools and gates.
includeUnavailable
Includes unavailable entries in discovery responses. Check further before execution.
includeInputSchema
Boolean switch. It changes which checks, data, or state transitions become visible.
| Response field | Explanation |
|---|---|
includeUnavailable | Boolean state or option signal. Read it together with status and surrounding context. |
includeInputSchema | Boolean state or option signal. Read it together with status and surrounding context. |
Safety
Boundary before execution
Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.
Use the response as current evidence, then choose a more specific next tool only after target, scope, and freshness are clear.
For humans, this entry explains what an agent reads in browser environment, window state, and isolated execution surfaces and which current signal should be checked before trusting the result.
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.
read_current_state
Reads current state, response signals, or evidence without treating that alone as permission for a follow-up action.
Use the signal as current evidence and re-check target, scope, and visible state before any follow-up action.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.