MCP Tool
nova.task_instance_create
For knowledge signals, learning candidates, and explainable orientation, an agent uses this public tool to carry out the bounded step "Instanz start". 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 Memory)
- Effect
- changes state
- Status
- Explained
- Path
- 13.3
Purpose
What this entry explains
What it does
nova.task_instance_create
An agent uses this tool to carry out the bounded step "Instanz start". It belongs to knowledge signals, learning candidates, and explainable orientation; 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 "Instanz start" for knowledge signals, learning candidates, and explainable orientation.
- 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 touches data, identity, or permissions in knowledge signals, learning candidates, and explainable orientation that may be used only with clear purpose.
The agent starts with nova.task_search, reads the current response or reference, and only then chooses the concrete next tool.
Sensitive values stay in current scope; they are not guessed, logged, or copied into other contexts.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
profileId
Profile reference for identity, knowledge, or task context. Do not guess it from memory.
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.
Treat stored knowledge as guidance only. Before any action, confirm the current page, target, scope, and visible evidence again.
For humans, this entry names the browser or workflow state in knowledge signals, learning candidates, and explainable orientation 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.persistent_change
Saves, deletes, remembers, schedules, or changes data that may outlive the immediate page state.
Execute only with clear scope and keep the saved, deleted, or scheduled effect reviewable.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.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.