MCP Tool
nova.crawl_diff
For bounded website review runs and discoverable result data, an agent uses this public tool to start or monitor the bounded flow "Crawl-Diff". 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
- Crawler & Site Discovery
- Effect
- bounded run
- Status
- Explained
- Path
- 9.7
Purpose
What this entry explains
What it does
nova.crawl_diff
An agent uses this tool to start or monitor the bounded flow "Crawl-Diff". It belongs to bounded website review runs and discoverable result data; 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-Diff" for bounded website review runs and discoverable result data.
- 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 bounded website review runs and discoverable result data can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.crawl_start, 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
No stable public input field is derived from the catalog source for this path. Read 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 bounded website review runs and discoverable result data 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.
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.