DE EN
Back to MCP catalog

MCP Tool

nova.tools_bundle

For visual regression, thresholds, and evidence bundles, an agent uses this public tool to check the state or evidence for "Bundle/Discovery". 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
Screenshot Diff (Visual Regression)
Effect
read-only
Status
Explained
Path
53.1

Purpose

What this entry explains

What it does

nova.tools_bundle An agent uses this tool to check the state or evidence for "Bundle/Discovery". It belongs to visual regression, thresholds, and evidence bundles; 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 "Bundle/Discovery" for visual regression, thresholds, and evidence bundles.
  • 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 user needs visual or media evidence in visual regression, thresholds, and evidence bundles without capturing private content unnecessarily.

The agent starts with nova.tools_bundle, reads the current response or reference, and only then chooses the concrete next tool.

Capture only needed evidence, keep recording state visible, and respect private content.

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

bundle

Tool-bundle name. Use discovery to see available tools and gates.

includeUnavailable

Includes unavailable entries in discovery responses. Check further before execution.

includeInputSchema

Boolean switch. It changes which checks, data, or state transitions become visible.

Response fieldExplanation
beforePathResponse field named by the catalog source. Treat it as current evidence for the next decision.
afterPathResponse field named by the catalog source. Treat it as current evidence for the next decision.
thresholdResponse field named by the catalog source. Treat it as current evidence for the next decision.
minRegionSizeResponse field named by the catalog source. Treat it as current evidence for the next decision.

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

Use the response as current evidence, then choose a more specific next tool only after target, scope, and freshness are clear.

Human control

For humans, this entry explains what an agent reads in visual regression, thresholds, and evidence bundles and which current signal should be checked before trusting the result.

High-Impact Review

Execution boundary and recheck hints

Review category: Recording/screenshots/media

Execution boundary

Capture only the needed visual or media evidence and respect private content, recording state, and export boundary.

Typical false assumption

False assumption: screenshots or recordings contain only technical evidence.

Visible user control

Recording, screenshot, media access, or export must be visible to the user and purpose-bound.

Agent rule

Before capture, check target, scope, and privacy; use artifacts as evidence only and do not forward them unrequested.

Abort or recheck

Abort if private content is visible, media permission is unclear, or the export contains more than needed.

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.
Recording / media recording_or_media

Creates or reads screenshots, recordings, media, visual evidence, or audio/video signals.

Capture only needed evidence, respect private content, and keep media or recording state visible.