MCP Tool
nova.crawl_verify
For visual evidence, screenshots, and reviewable differences, an agent uses this public tool to start or monitor the bounded flow "Crawl-Verify Highlight". It names the scope, progress signal, stopping condition, and result check that keep the run bounded.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Screenshot Markings & Visual Aids
- Effect
- bounded run
- Status
- Explained
- Path
- 49.4
Purpose
What this entry explains
What it does
nova.crawl_verify
An agent uses this tool to start or monitor the bounded flow "Crawl-Verify Highlight". 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 start or monitor the bounded flow "Crawl-Verify Highlight" 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.capture_screenshot, 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
screenshotHighlight
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
Starts or observes a bounded run. Scope, limits, progress, and terminal status need to stay visible.
Set scope and limits before starting the run, poll explicit progress or status fields, and stop instead of assuming completion.
For humans, this entry shows which bounded flow in visual evidence, screenshots, and reviewable differences starts or continues, and where scope, progress, and stopping conditions belong.
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.
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.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.automation_run
Starts or monitors crawls, sequences, schedulers, tasks, batches, or longer runs.
Keep scope, budget, progress, stop condition, and terminal status visible before and during the run.