MCP Path
Finalizing Linger
Finalizing Linger is a public reference for bounded website review runs and discoverable result data. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.
Reference page for a documented MCP capability path.
- Type
- MCP path
- Family
- Crawler & Site Discovery
- Effect
- read-only
- Status
- Reference
- Path
- 9.26
Purpose
What this entry explains
What it does
This reference explains Finalizing Linger for bounded website review runs and discoverable result data. It is kept as a named reference so agents can cite the flow without inventing a tool name.
Use when
- Use this entry when an agent needs to check the state or evidence for "Finalizing Linger" for bounded website review runs and discoverable result data.
- Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
- 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.
Finalizing Linger describes a signal for bounded website review runs and discoverable result data. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.
An agent cites this path when it needs Finalizing Linger as context for a decision, block, target check, or follow-up tool choice.
The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.
Relevant response signals: crawl_stop, crawl_update, crawl.finalizing_read_only, resultsComplete. Safety axes: Read current state, Automation. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.
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 field | Explanation |
|---|---|
crawl_stop | Response field named by the catalog source. Treat it as current evidence for the next decision. |
crawl_update | Response field named by the catalog source. Treat it as current evidence for the next decision. |
crawl.finalizing_read_only | Response field named by the catalog source. Treat it as current evidence for the next decision. |
resultsComplete | Response field named by the catalog source. Treat it as current evidence for the next decision. |
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 bounded website review runs and discoverable result data and which current signal should be checked before trusting the result.
High-Impact Review
Execution boundary and recheck hints
Review category: Scheduler/tasks/automation
Runs need scope, budget, progress, stop condition, and reviewable terminal status before they start or continue.
False assumption: once started, a run may continue until success.
Task, schedule, variables, workspace, and run status must remain reviewable by the user.
Bound automations, poll progress, check terminal status, and avoid chaining when results are unclear.
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.
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.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.