jevpilot

browser_navigate

Navigate a specified URL within an active browser session tab, restricted to that session's domain allowlist.

Instructions

Navigate the selected session tab within its domain allowlist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>",
      "url": "<url>"
    },
    "name": "browser_navigate"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`session`	Yes	Session ID returned by browser_run.

Output Schema

Name	Required	Description	Default
`url`	Yes
`title`	Yes
`trace`	Yes
`usage`	Yes
`reason`	Yes
`status`	Yes
`timing`	Yes
`details`	No
`session`	Yes
`question`	Yes
`snapshot`	Yes
`screenshot_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Oct 1, 2026

changedOutput schema / properties / trace / items / properties / outcome / enum

Previous value: -[
-  "changed",
-  "unchanged",
-  "stale",
-  "covered",
-  "disabled",
-  "invisible",
-  "not-editable",
-  "unstable",
-  "select-failed",
-  "dialog-opened",
-  "value-not-set",
-  "accepted",
-  "dismissed"
-]New value: +[
+  "changed",
+  "unchanged",
+  "stale",
+  "covered",
+  "disabled",
+  "invisible",
+  "not-editable",
+  "unstable",
+  "select-failed",
+  "dialog-opened",
+  "value-not-set",
+  "not-focusable",
+  "accepted",
+  "dismissed"
+]

First observedv0.1.0Sep 29, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It does disclose one real constraint, the domain allowlist, which is valuable, but says nothing about load/wait behavior, failure modes when a URL is rejected, or whether history is appended.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though its brevity contributes to the undisclosed behavior rather than being purely a virtue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, which lowers the bar. Still, for a state-changing navigation tool with no annotations, more detail on the allowlist failure behavior and session prerequisites would be needed to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the session parameter is documented in the schema, while url only carries a uri format. The description adds meaning to url by constraining it to the session's domain allowlist, which the schema does not express, but gives no further syntax or format guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (navigate) and resource (the selected session tab), plus the scope constraint of a domain allowlist. It does not explicitly differentiate itself from siblings like browser_act or browser_run, which an agent might also use to move a page, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. The phrase 'selected session tab' implies a session must already be chosen, but nothing tells the agent how to arrive at that state or when to prefer this over browser_act.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server