MCP Tool
nova.scheduled_task_run_output
For prepared tasks, runs, and closed-loop automation steps, an agent uses this public tool to carry out the bounded step "Run Output Tail Read". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Scheduled Tasks
- Effect
- changes state
- Status
- Explained
- Path
- 17.20
Purpose
What this entry explains
What it does
nova.scheduled_task_run_output
An agent uses this tool to carry out the bounded step "Run Output Tail Read". It belongs to prepared tasks, runs, and closed-loop automation steps; 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 "Run Output Tail Read" for prepared tasks, runs, and closed-loop automation steps.
- 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 prepared tasks, runs, and closed-loop automation steps can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.scheduled_task_create, 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
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 prepared tasks, runs, and closed-loop automation steps 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.
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.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.