MCP Tool
nova.pks_platform_seed
For knowledge signals, learning candidates, and explainable orientation, an agent uses this public tool to carry out the bounded step "Platform Seed". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Platform PKS (Cross-Domain Knowledge)
- Effect
- changes state
- Status
- Explained
- Path
- 32.1
Purpose
What this entry explains
What it does
nova.pks_platform_seed
An agent uses this tool to carry out the bounded step "Platform Seed". 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 "Platform Seed" 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 evaluate an external source or connection in knowledge signals, learning candidates, and explainable orientation before it becomes part of a tool chain.
The agent starts with nova.pks_platform_seed, reads the current response or reference, and only then chooses the concrete next tool.
External targets and transports are confirmed before use; third-party tools are not silently chained.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
patterns
Public input field from the catalog source. Confirm the exact schema through current MCP discovery before execution.
aliases
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
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: Proxy/external connection
External targets, proxies, gateways, and transport paths may be used only with checked target, status, and approval.
False assumption: a reachable external tool is automatically part of the allowed Nova tool chain.
Target, transport status, import or connection approval, and expected data movement must be visible.
Do not silently add third-party tools; check current approval, target, and response status before use.
Recheck if the gateway, proxy, remote source, or target system changes or emits warnings.
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.external_connection
Uses proxy, external MCP gateways, network routes, third-party integrations, or import paths.
Check external target, transport status, and approval before use; do not silently chain third-party tools.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.