Skip to main content
Glama
dlwjdtn535

mcp-chrome-server

tool_navigate

Navigate the browser to any URL, automatically opening a browser if none is open. Input a valid URL with protocol to start browsing.

Instructions

Navigate to a URL.

    This tool navigates the browser to the specified URL. If no browser
    is open, it will automatically open one.
    
    Args:
        url (str): The URL to navigate to (must include protocol, e.g., 'https://')
    
    Returns:
        Dict[str, Any]: A dictionary containing:
            - success (bool): Whether the operation was successful
            - message (str): Status message
    
    Example:
        {"tool": "navigate", "args": {"url": "https://www.example.com"}}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
Behavior4/5

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

No annotations provided, so the description carries the burden. It discloses auto-opening behavior and the protocol requirement, but does not mention error handling or potential side effects like navigation timeouts.

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?

The description is structured with Args/Returns/Example and is mostly concise, but has slight redundancy (the first sentence restates the title and the second sentence repeats it). Minimally verbose for the clarity it provides.

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 no output schema, the description provides the return format and an example. It lacks detailed error handling but covers the primary use case sufficiently for a navigation tool with one parameter.

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

Parameters5/5

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

With schema coverage at 0% (no description in schema), the description adds critical information: that the URL must include protocol (e.g., 'https://'), which is essential for correct invocation beyond the schema's basic type definition.

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 navigates to a URL and distinguishes it from siblings like tool_back, tool_forward, and tool_refresh by specifying the 'navigate' verb and the resource 'URL'.

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 mentions auto-opening a browser if none is open, implying when to use it, but lacks explicit guidance on when not to use it or how it compares to alternatives like tool_open_browser or tool_refresh.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dlwjdtn535/mcp-chrome-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server