MCP Tool
nova.task_instance_reconcile_coverage
For URL coverage, evidence, and completion gates, an agent uses this public tool to carry out the bounded step "Reconcile Coverage Dry Run". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- ETM Task URL Coverage (Feature Request)
- Effect
- changes state
- Status
- Explained
- Path
- 54.20
Purpose
What this entry explains
What it does
nova.task_instance_reconcile_coverage
An agent uses this tool to carry out the bounded step "Reconcile Coverage Dry Run". It belongs to URL coverage, evidence, and completion gates; 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 "Reconcile Coverage Dry Run" for URL coverage, evidence, and completion gates.
- 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 URL coverage, evidence, and completion gates can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.coverage_scan, 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
dryRun
Public input field from the catalog source. Confirm the exact schema through current MCP discovery before execution.
| Response field | Explanation |
|---|---|
dryRun | Response field named by the catalog source. Treat it as current evidence for the next decision. |
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 URL coverage, evidence, and completion gates 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
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.
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_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.