Skip to main content
Glama
Intrect-io

lyra-browser

Official
by Intrect-io

navigate

Move the shared browser to a URL. Requests permission for cross-site and local URLs, reports HTTP status and content type, and can save downloads with confirmation.

Instructions

Navigate the shared window to a URL.

Going to a different site asks for permission to be on that site. Moving within the current one does not. A URL with no host — file:, data:, javascript: — is never "the same site" and is always asked, every time, because one approval there would cover every local file or every document the agent can author.

ok means the navigation happened, not that the page is good: read http_status (404, 500 ...) and content_type (application/pdf ...) of the page that answered. Both are null when no HTTP response was involved (about:blank, data:). wait_until is how much of the load to wait for: domcontentloaded (default), load, commit or networkidle — which never settles on a page that keeps polling. A page that draws itself after it has loaded needs wait_for. A URL that turns out to be a file download does not move the tab: with download=true — which asks for permission to write a file — it is saved and the reply carries download (filename, path, bytes, url_origin); without it the download is cancelled and answered download_blocked, so repeat the call with download=true. The permission pays for one file and ends with the call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
reasonNo
confirmNo
downloadNo
wait_untilNodomcontentloaded

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the permission model and its scope ('pays for one file and ends with the call'), what ok does and does not mean, when http_status/content_type are null, and the wait_until/networkidle caveat. This is unusually rich behavioral disclosure for a mutation-like tool.

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?

Dense and front-loaded: purpose, then permission rules, then result reading, then timing, then downloads. Nearly every sentence earns its place, though the length is on the edge of excessive for a single navigation call.

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?

An output schema exists, yet the description still explains the reply fields (ok, http_status, content_type, download) which is helpful rather than harmful. The main completeness gap is the unexplained confirm/reason parameters, which matter given the tool's permission-approval behavior.

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?

Schema coverage is 0%, so the description must compensate, and it explains url, download, and wait_until in depth — including the valid wait_until values, which the schema itself does not enumerate. However, the 'confirm' and 'reason' parameters are never mentioned, leaving two of five parameters undocumented despite the permission-approval storyline implying confirm's role.

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?

Opens with a specific verb and resource ('Navigate the shared window to a URL'), which is distinct from siblings such as go_back, reload_page, and get_url. An agent can immediately tell this is the tool that performs a fresh navigation rather than a history/read operation.

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?

Gives clear conditional guidance: same-site moves are unasked, cross-site moves ask permission, and host-less schemes (file:, data:, javascript:) always ask. It also explains the download=true workaround when a call returns download_blocked. It stops short of naming sibling alternatives (e.g., go_back/reload_page) explicitly.

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