MCP Path
Identische PNGs
Identische PNGs is a public reference for visual regression, thresholds, and evidence bundles. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.
Reference page for a documented MCP capability path.
- Type
- MCP path
- Family
- Screenshot Diff (Visual Regression)
- Effect
- read-only
- Status
- Reference
- Path
- 53.2
Purpose
What this entry explains
What it does
This reference explains Identische PNGs for visual regression, thresholds, and evidence bundles. It is kept as a named reference so agents can cite the flow without inventing a tool name.
Use when
- Use this entry when an agent needs to check the state or evidence for "Identische PNGs" for visual regression, thresholds, and evidence bundles.
- Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
- 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.
Identische PNGs describes a signal for visual regression, thresholds, and evidence bundles. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.
An agent cites this path when it needs Identische PNGs as context for a decision, block, target check, or follow-up tool choice.
The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.
Relevant response signals: pixelDiffPercent, changedRegions. Safety axes: Read current state, Recording / media. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.
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
No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.
| Response field | Explanation |
|---|---|
pixelDiffPercent | Response field named by the catalog source. Treat it as current evidence for the next decision. |
changedRegions | Response field named by the catalog source. Treat it as current evidence for the next decision. |
Safety
Boundary before execution
Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.
Use the response as current evidence, then choose a more specific next tool only after target, scope, and freshness are clear.
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
Capture only the needed visual or media evidence and respect private content, recording state, and export boundary.
False assumption: screenshots or recordings contain only technical evidence.
Recording, screenshot, media access, or export must be visible to the user and purpose-bound.
Before capture, check target, scope, and privacy; use artifacts as evidence only and do not forward them unrequested.
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
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_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.