MCP Tool

`nova.route`

For parameter validation, alias conflicts, and robust failure paths, an agent uses this public tool to carry out the bounded step "Concurrent Route Conflict". It separates target confirmation, intended state change, and verification after execution.

Agent tool

Canonical reference for a public MCP tool name.

Type: MCP tool
Family: Edge Cases & Error Paths
Effect: changes state
Status: Explained
Path: 51.12

Purpose

What this entry explains

What it does

nova.route An agent uses this tool to carry out the bounded step "Concurrent Route Conflict". It belongs to parameter validation, alias conflicts, and robust failure paths; 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 "Concurrent Route Conflict" for parameter validation, alias conflicts, and robust failure paths.
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 in parameter validation, alias conflicts, and robust failure paths can trigger powerful execution and therefore needs target, approval, and result check before the step.

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

nova.perceive nova.tab_claim nova.tab_release

Current discovery, target, user control, warning signals, and result check come before execution.

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
`route.concurrent_conflict`	Response field named by the catalog source. Treat it as current evidence for the next decision.
`retryAfterMs`	Response field named by the catalog source. Treat it as current evidence for the next decision.

Safety

Boundary before execution

Effect

Can change browser, page, or workflow state. The target and expected result must be clear before execution.

Agent rule

Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.

Human control

For humans, this entry names the browser or workflow state in parameter validation, alias conflicts, and robust failure paths that may change, so the action can be reviewed before and after execution.

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 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.

nova.route