MCP Tool
nova.app_info
For connection setup, tool discovery, and transport readiness, an agent uses this public tool to carry out the bounded step "App-Info Build/Runtime Diagnostics". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Basics & Session
- Effect
- changes state
- Status
- Explained
- Path
- 1.6
Purpose
What this entry explains
What it does
nova.app_info
An agent uses this tool to carry out the bounded step "App-Info Build/Runtime Diagnostics". It belongs to connection setup, tool discovery, and transport readiness; 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 "App-Info Build/Runtime Diagnostics" for connection setup, tool discovery, and transport readiness.
- 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 connection setup, tool discovery, and transport readiness that may be used only with clear purpose.
The agent starts with initialize, 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
No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.
| Response field | Explanation |
|---|---|
structuredContent.build | Response field named by the catalog source. Treat it as current evidence for the next decision. |
structuredContent.runtime | Runtime or communication signal for agent-facing integrations. It is not a normal human UI control. |
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.
For humans, this entry names the browser or workflow state in connection setup, tool discovery, and transport readiness that may change, so the action can be reviewed before and after execution.
High-Impact Review
Execution boundary and recheck hints
Review category: Eval/CDP/diagnostics
Run only on the currently confirmed target; expression, expected result, and visible context must be clear before the call.
False assumption: because a script is intended to read, the path is automatically harmless.
The user must be able to see which page is targeted and why code, CDP, or diagnostics are being run.
Before execution, check current discovery, target, expression, and stop signal; do not derive additional scripts from the result.
Abort or recheck if the target changed, the expression touches third-party data, or the response contains 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
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.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.