Local MCP

Web Navigate

web_navigate

Navigates a web session to a URL (using its saved login if any) and returns the resulting URL + page title. Opens the session if it doesn't exist. CHECK loaded before reading: when it is false the page did not load and message says why — reading the session then describes a blank document, not the site. Read the page with web_read.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	URL to open (https).
`session`	No	Session name (default 'default').
`timeout_seconds`	No	Max seconds to wait for load (default 25).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	True only when the requested page actually loaded.
`url`	No	The URL the browser settled on (redirects followed). If it isn't the page you asked for, the navigation didn't deliver it.
`error`	No	Present only on failure: nav_failed (the browser rejected the load), nav_timeout, or nav_blank (it finished on a blank document).
`title`	No	The resulting page title.
`loaded`	No	True only when the browser ended on a real web page. False means nothing was loaded — do NOT read the session and treat the result as page content.
`message`	No	Present only on failure: why the page didn't load, and what to do about it.
`settle_rejected_by`	No	Present only with nav_timeout: which check ruled out 'the page arrived and WebKit just did not say so' - navigation_started (another navigation began and hung, so the visible document is the old one), other_url (it settled on a different page), or not_complete (the document never finished parsing).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

addedOutput schema / properties / settle_rejected_by

Added value: +{
+  "description": "Present only with nav_timeout: which check ruled out 'the page arrived and WebKit just did not say so' - navigation_started (another navigation began and hung, so the visible document is the old one), other_url (it settled on a different page), or not_complete (the document never finished parsing).",
+  "type": "string"
+}

Changed5 schema fields changedAug 20, 2026

addedOutput schema / properties / error

Added value: +{
+  "description": "Present only on failure: nav_failed (the browser rejected the load), nav_timeout, or nav_blank (it finished on a blank document).",
+  "type": "string"
+}

addedOutput schema / properties / loaded / description

Added value: +"True only when the browser ended on a real web page. False means nothing was loaded — do NOT read the session and treat the result as page content."

addedOutput schema / properties / message

Added value: +{
+  "description": "Present only on failure: why the page didn't load, and what to do about it.",
+  "type": "string"
+}

changedOutput schema / properties / ok / description

Previous value: -"True when the page finished loading."New value: +"True only when the requested page actually loaded."

changedOutput schema / properties / url / description

Previous value: -"The URL after navigation (redirects followed)."New value: +"The URL the browser settled on (redirects followed). If it isn't the page you asked for, the navigation didn't deliver it."

Changed1 schema field changedJul 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "loaded": {
+      "type": "boolean"
+    },
+    "ok": {
+      "description": "True when the page finished loading.",
+      "type": "boolean"
+    },
+    "title": {
+      "description": "The resulting page title.",
+      "type": "string"
+    },
+    "url": {
+      "description": "The URL after navigation (redirects followed).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses that it opens a session if none exists and returns the resulting URL and title. It also transparently explains the `loaded` flag behavior and warns about reading a blank document on failure. This covers the main side effects but omits details about error handling or waiting behavior.

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

Conciseness5/5

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

The description is succinct and well-structured, front-loading the core action and then adding important usage cautions. Each sentence contributes meaningful information without redundancy.

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

Completeness4/5

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

Given an output schema is present, the description appropriately focuses on usage context rather than return values. It covers the main scenario (navigate to URL, check loaded, then read), which is sufficient for an agent to decide when to use this tool. Some edge cases like login failures are not detailed, but the description gives enough for typical use.

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

Parameters4/5

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

The schema already provides 100% coverage of the three parameters with descriptions. The description adds value by clarifying that the session parameter is auto-opened if it doesn't exist, and that saved login credentials are used – details not fully captured in the schema.

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

Purpose5/5

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

The description clearly states the tool's verb (navigates), resource (web session), and specific outcome (returns URL and page title). It also differentiates from sibling tools by explicitly pointing to web_read for reading the page content.

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

Usage Guidelines4/5

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

The description provides explicit guidance on checking the `loaded` flag before reading and directs the user to web_read. It implies this is the tool to use for navigating to a new URL, but does not explicitly contrast with alternative navigation-related tools like web_find or web_extract.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.