MCP Tool
nova.pks_patch
For knowledge signals, learning candidates, and explainable orientation, an agent uses this public tool to check the state or evidence for "Phenomenon patchen". 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
- PKS (Knowledge Store)
- Effect
- read-only
- Status
- Explained
- Path
- 10.4
Purpose
What this entry explains
What it does
nova.pks_patch
An agent uses this tool to check the state or evidence for "Phenomenon patchen". 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 check the state or evidence for "Phenomenon patchen" 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
An agent needs to change visible state in knowledge signals, learning candidates, and explainable orientation without guessing target or result from an earlier session.
The agent starts with nova.pks_upsert, reads the current response or reference, and only then chooses the concrete next tool.
Change only the confirmed target, then check visible state and stop on mismatch.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
scope
Public input field from the catalog source. Confirm the exact schema through current MCP discovery before execution.
phenomenonId
Reference key for the current target, object, or session. Read it from the current response instead of guessing.
patch
Public input field from the catalog source. Confirm the exact schema through 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
Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.
Treat stored knowledge as guidance only. Before any action, confirm the current page, target, scope, and visible evidence again.
For humans, this entry explains what an agent reads in knowledge signals, learning candidates, and explainable orientation and which current signal should be checked before trusting the result.
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.