@nxavis/agent-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_navigate

Navigate to a specified URL in an automated browser. Use session IDs to isolate browsing contexts for parallel operations.

Instructions

Navigate to a URL in the browser

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": "browser_navigate"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL to navigate to
`sessionId`	No	Browser session ID for isolation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action without revealing any side effects, page load behavior, or session isolation semantics. This provides minimal transparency beyond the basic intent.

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 a single, concise sentence that front-loads the essential verb and resource. No wasted words, and the structure is immediately scannable.

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?

Given the tool's simplicity and full schema coverage, the description is minimally sufficient but lacks behavioral context like whether it waits for page load or how sessionId affects isolation. It is not incomplete enough to hinder basic usage, but more context could improve understanding.

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 input schema provides 100% coverage with descriptions for both 'url' and 'sessionId', so the description adds no further parameter meaning. Baseline 3 is appropriate as the schema handles parameter semantics adequately.

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 action (navigate) and the resource (a URL), which is specific and distinct from sibling tools like browser_go_back, browser_go_forward, and browser_reload. It unambiguously identifies the tool's primary function.

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

Usage Guidelines3/5

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

The description implies usage for loading a specific URL, which is distinct from history navigation (go_back/go_forward) and reload. However, it does not explicitly state when not to use it or call out alternatives, relying on the sibling tool names to convey context.

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