MCP Tool

`nova.discovery_reset_scope`

For bounded website review runs and discoverable result data, an agent uses this public tool to carry out the bounded step "Discovery Reset". It separates target confirmation, intended state change, and verification after execution.

Agent tool

Canonical reference for a public MCP tool name.

Type: MCP tool
Family: Crawler & Site Discovery
Effect: changes state
Status: Explained
Path: 9.12

Purpose

What this entry explains

What it does

nova.discovery_reset_scope An agent uses this tool to carry out the bounded step "Discovery Reset". 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 carry out the bounded step "Discovery Reset" 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.

nova.crawl_start nova.crawl_status nova.crawl_results

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

domain

Domain or scope value for site-specific queries.

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

Effect

Can change browser, page, or workflow state. The target and expected result must be clear before execution.

Agent rule

Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.

Human control

For humans, this entry names the browser or workflow state in bounded website review runs and discoverable result data that may change, so the action can be reviewed before and after execution.

High-Impact Review

Execution boundary and recheck hints

Review category: Scheduler/tasks/automation

Execution boundary

Runs need scope, budget, progress, stop condition, and reviewable terminal status before they start or continue.

Typical false assumption

False assumption: once started, a run may continue until success.

Visible user control

Task, schedule, variables, workspace, and run status must remain reviewable by the user.

Agent rule

Bound automations, poll progress, check terminal status, and avoid chaining when results are unclear.

Abort or recheck

Abort or recheck when budget, target set, run ID, workspace, or result status becomes unclear.

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 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.

Automation 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.

High-impact execution high_impact_execution

Runs or prepares JavaScript, CDP, plugin code, auto-apply, or other powerful execution paths.

Explicitly confirm current tool discovery, target, scope, user control, and result check before execution.

User confirmation user_confirmation

Requires visible confirmation, target review, approval, or deliberate user control.

Do not proceed until the required confirmation is visible or unambiguous in the current context.

nova.discovery_reset_scope