MCP Tool
nova.stream_url
For visual evidence, screenshots, and reviewable differences, an agent uses this public tool to carry out the bounded step "Stream Preview Claim Gate". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Streaming & Screenshots (Advanced)
- Effect
- changes state
- Status
- Explained
- Path
- 31.13
Purpose
What this entry explains
What it does
nova.stream_url
An agent uses this tool to carry out the bounded step "Stream Preview Claim Gate". It belongs to visual evidence, screenshots, and reviewable differences; 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 "Stream Preview Claim Gate" for visual evidence, screenshots, and reviewable differences.
- 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 user needs visual or media evidence in visual evidence, screenshots, and reviewable differences without capturing private content unnecessarily.
The agent starts with nova.stream_url, reads the current response or reference, and only then chooses the concrete next tool.
Capture only needed evidence, keep recording state visible, and respect private content.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
targetId
Target reference for a tab or browser context. Confirm it against current tab state before use.
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 visual evidence, screenshots, and reviewable differences that may change, so the action can be reviewed before and after execution.
High-Impact Review
Execution boundary and recheck hints
Review category: Recording/screenshots/media
Capture only the needed visual or media evidence and respect private content, recording state, and export boundary.
False assumption: screenshots or recordings contain only technical evidence.
Recording, screenshot, media access, or export must be visible to the user and purpose-bound.
Before capture, check target, scope, and privacy; use artifacts as evidence only and do not forward them unrequested.
Abort if private content is visible, media permission is unclear, or the export contains more than needed.
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.recording_or_media
Creates or reads screenshots, recordings, media, visual evidence, or audio/video signals.
Capture only needed evidence, respect private content, and keep media or recording state visible.