dawg-mcp

by dawgswarm

Overview Schema Source Related Servers Discussions Admin

Python

Remote

browser_navigate

Loads a URL in the active browser tab and provides an updated AI snapshot of the page.

Instructions

Navigate the active page to a URL. Returns a fresh AI snapshot.

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
`session_id`	No
`timeout_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

C2.7/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It mentions returning a fresh snapshot, which is a behavioral detail. However, it does not mention error handling, loading states, or that the previous page is replaced.

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 very short (one sentence plus a brief result mention), making it concise. However, it could include more structure, such as listing parameters or usage examples.

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?

Given the lack of annotations and output schema, the description is insufficient. It does not cover required parameters, error scenarios, or how it relates to sibling navigation tools. The tool appears to be part of a complex browser suite, and the description is too sparse.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate. It fails to explain any of the three parameters (url format, session_id usage, timeout meaning). This is a critical gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it navigates to a URL, which distinguishes it from other browser tools like navigate_back/forward and snapshot. However, it does not explicitly differentiate from similar navigation commands like 'browser_tabs' or mention that it sets the active page.

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 navigate_back/forward or whether a browser session must be provisioned first. The description lacks context for appropriate usage.

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