Skip to main content
Glama
feder-cr

AIHawk

Official
by feder-cr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_navigate

Destructive

Navigate to a URL in a live browser, returning the HTTP status and final URL after redirects. Choose when to consider the page loaded using domcontentloaded, load, or networkidle.

Instructions

Go to a url in this browser's page, opening it if none exists.

Answers with the HTTP status the server gave and the url actually landed on, which is not always the one asked for: a redirect to a login wall or a regional domain shows up here. Read the status before trusting the page - a 404 or a 403 still has a document, and reading it as content is the mistake this reply exists to prevent.

wait_until is "domcontentloaded" by default, which returns as soon as the markup is parsed. Use "load" when the page needs its images and stylesheets, or "networkidle" for a single-page app that fetches its content after load.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
browserNoDefaults to `main`; `support` is the helper beside it.
wait_untilNodomcontentloaded

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.68.0
    • addedInput schema / properties / browser / description
      Added value: +"Defaults to `main`; `support` is the helper beside it."
  2. First observedv0.43.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations, explaining that the tool returns the HTTP status and final landed URL, that redirects may lead to login walls or regional domains, and that 404/403 pages still have a document. It also discloses default and alternative wait_until behaviors. This is substantial value beyond the structured annotations.

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 front-loaded with the core action, then layers in critical response semantics and parameter behavior. Every sentence adds necessary information, and there is no redundant or filler content. It is detailed without being bloated.

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

Completeness5/5

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

For a navigation tool with 3 parameters, the description covers the required behavior, return value highlights, and parameter tuning options. The presence of an output schema reduces the need to describe return fields, and the description still provides useful context about interpreting status codes. Nothing essential is missing for an agent to invoke the tool correctly.

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 only 33%, and the description compensates by thoroughly explaining wait_until values and their behavioral implications. The 'url' parameter is contextually implied as the destination URL, and the 'browser' parameter is already described in the schema. It does not add formal URL format guidance, but the provided semantics are sufficient for correct invocation.

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 states a specific verb and resource: 'Go to a url in this browser's page, opening it if none exists.' It clearly differentiates from sibling tools by emphasizing navigation within an existing page and the ability to open one if needed. The title and description align without being tautological.

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 gives clear context on when to use this tool and how to tune wait_until for different page types, such as 'load' for images and stylesheets or 'networkidle' for single-page apps. It does not explicitly name sibling alternatives or exclusion cases, but the behavioral context is strong enough to guide selection.

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

Deploy Server

Other Tools