veilbrowser

veil_goto

Navigate to a URL in a stealth browser, launching Chrome on first call. Supports wait until page load or network idle for SPAs.

Instructions

Navigate the browser to a URL (launches Chrome on first call). waitUntil 'load' (default) or 'networkidle' (wait until no network for ~500ms — better for SPAs that fetch after load).

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": {
      "url": "<url>"
    },
    "name": "veil_goto"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`waitUntil`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description discloses key behaviors: browser launch on first call and the two waitUntil options with their implications. It lacks details on error handling or security restrictions, but covers the main behavioral aspects.

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?

Two concise sentences. The first states the core purpose, the second provides critical parameter context. No superfluous text.

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?

For a navigation tool with 2 parameters and no output schema, the description covers usage, param options, and a notable side effect. Lacks mention of return value or typical errors, but is reasonably 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?

The description explains the waitUntil enum values with behavior, but does not clarify the url parameter beyond 'URL'. Since schema description coverage is 0%, the description partially compensates (50% of parameters explained), but could add more detail on expected URL format.

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 primary action: 'Navigate the browser to a URL'. It distinguishes this from sibling navigation tools (veil_reload, veil_back, veil_forward) by focusing on loading a new URL, and mentions the browser launch side effect.

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 guidance on when to use each waitUntil option ('better for SPAs that fetch after load'), but does not explicitly contrast with sibling tools or state conditions when not to use this tool.

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