MCP Tool
nova.notifications_send
For user artifacts, notices, and small work handoffs, an agent uses this public tool to check the state or evidence for "Notification Send HighImpact". 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
- Notifications
- Effect
- read-only
- Status
- Explained
- Path
- 18.11
Purpose
What this entry explains
What it does
nova.notifications_send
An agent uses this tool to check the state or evidence for "Notification Send HighImpact". It belongs to user artifacts, notices, and small work handoffs; 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 "Notification Send HighImpact" for user artifacts, notices, and small work handoffs.
- 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 user artifacts, notices, and small work handoffs can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.notifications_send, 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 |
|---|---|
structuredContent | Structured response area for agents and integrations. |
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 user artifacts, notices, and small work handoffs and which current signal should be checked before trusting the result.
High-Impact Review
Execution boundary and recheck hints
Review category: High-impact execution
Execute only with current discovery, confirmed target, clear scope, and visible result check.
False assumption: a successful response signal automatically permits the next powerful step.
Target, effect, and approval must remain visible before and after execution.
Treat warnings, blocks, and scope signals first; do not continue from memory.
Stop when target, scope, status, or user approval is no longer unambiguous.
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.high_impact_execution
Runs or prepares JavaScript, CDP, plugin code, auto-apply, or other powerful execution paths.
Explicitly confirm current tool discovery, target, scope, user control, and result check before execution.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.