Skip to main content
Glama

navigate

Navigate to a specific URL to begin or continue web application testing with automated verification.

Instructions

Navigate to a specific URL.

Args: url: The URL to navigate to

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The navigate tool handler: takes a URL, navigates the browser to it via goto(), updates session state (steps, elements, pages_visited), and returns the resulting page URL, title, and element count.
    @mcp.tool()
    async def navigate(url: str) -> str:
        """Navigate to a specific URL.
    
        Args:
            url: The URL to navigate to
        """
        s = _require_session()
        step = f"Navigate to {url}"
        s.steps.append(step)
    
        await s.browser.goto(url)
        state = await s.browser.get_state()
        s._last_elements = state.elements
        if state.url not in s.pages_visited:
            s.pages_visited.append(state.url)
    
        return f"Navigated to {state.url} — {state.title} ({len(state.elements)} elements)"
  • Registration of the navigate tool using the @mcp.tool() decorator on the async function.
    @mcp.tool()
  • Helper function that ensures an active session exists before the navigate tool can be used.
    def _require_session() -> Session:
        if not _session.active:
            raise RuntimeError("No active session. Call start_session(url) first.")
        return _session
  • Schema/input definition: the tool accepts a single 'url' string parameter.
    """Navigate to a specific URL.
    
    Args:
        url: The URL to navigate to
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It fails to mention if page load is awaited, potential failure modes, or side effects like session state changes. Only states 'navigate' without elaboration.

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?

Extremely concise with no wasted words. Front-loads the purpose in the first line, then briefly documents the parameter. Every sentence earns its place.

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

Completeness2/5

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

Despite having an output schema, the description lacks critical context for a navigation tool, such as whether it waits for page load, handles redirects, or errors. This incompleteness could lead to incorrect usage.

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?

The description adds meaning to the single parameter 'url' by labeling it as 'The URL to navigate to'. Given 0% schema coverage, this provides clarity, though more detail (e.g., expected format) would be beneficial.

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 specific URL, which is a specific verb and resource. It distinguishes from siblings like 'go_back' and 'click' by focusing on direct URL navigation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'go_back' or 'crawl_site'. The description only states what it does, not when it is appropriate or when to avoid it.

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/chriswu727/argus'

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