MCP Tool
nova.coverage_scan
For URL coverage, evidence, and completion gates, an agent uses this public tool to check the state or evidence for "Coverage Scan Registered Evidence". It explains which current signal can be used as evidence and when a follow-up step needs a fresh target check.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- ETM Task URL Coverage (Feature Request)
- Effect
- read-only
- Status
- Explained
- Path
- 54.18
Purpose
What this entry explains
What it does
nova.coverage_scan
An agent uses this tool to check the state or evidence for "Coverage Scan Registered Evidence". 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 check the state or evidence for "Coverage Scan Registered Evidence" 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
scanId
Reference key for the current target, object, or session. Read it from the current response instead of guessing.
| Response field | Explanation |
|---|---|
scanHash | Artifact or evidence reference. Do not publish local values; use it for lookup, lifetime, or review context. |
textCoverageRatio | 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 URL coverage, evidence, and completion gates 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.