DE EN
Back to MCP catalog

MCP Tool

nova.pks_platform_get

For knowledge signals, learning candidates, and explainable orientation, an agent uses this public tool to check the state or evidence for "Platform Get". It explains which current signal can be used as evidence and when a follow-up step needs a fresh target check.

Agent tool

Canonical reference for a public MCP tool name.

Type
MCP tool
Family
Platform PKS (Cross-Domain Knowledge)
Effect
read-only
Status
Explained
Path
32.2

Purpose

What this entry explains

What it does

nova.pks_platform_get An agent uses this tool to check the state or evidence for "Platform Get". 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 "Platform Get" 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

stableId

Reference key for the current target, object, or session. Read it from the current response instead of guessing.

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

Effect

Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.

Agent rule

Treat stored knowledge as guidance only. Before any action, confirm the current page, target, scope, and visible evidence again.

Human control

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.

High-Impact Review

Execution boundary and recheck hints

Review category: Proxy/external connection

Execution boundary

External targets, proxies, gateways, and transport paths may be used only with checked target, status, and approval.

Typical false assumption

False assumption: a reachable external tool is automatically part of the allowed Nova tool chain.

Visible user control

Target, transport status, import or connection approval, and expected data movement must be visible.

Agent rule

Do not silently add third-party tools; check current approval, target, and response status before use.

Abort or recheck

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.

Read current state 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.
External 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 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.