Ceki

browser-navigate

Navigate a rented Chrome browser to any URL with a configurable timeout.

Instructions

Navigate the rented browser to a URL.

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	Full URL to navigate to (https://...)
`timeout`	No	Timeout in ms (default 30000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 26, 2026

TDQS

B3/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only states the basic action without detailing behaviors like waiting for page load, handling errors, or what happens to the current page. This is insufficient for a navigation tool.

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 with no superfluous words. It gets straight to the point.

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 output schema and annotations, the description fails to provide essential context about behavior, return values, or side effects. An agent cannot infer important details like loading completion or error handling from this minimal text.

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 has 100% description coverage, so the description adds minimal meaning beyond it. The description mentions 'to a URL' but does not add new semantic context beyond the parameter descriptions.

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 the rented browser to a URL.' It uses a specific verb (navigate) and identifies the resource (rented browser to a URL). This distinguishes it from sibling tools like browser-click or browser-scroll.

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 is provided on when to use this tool versus alternatives such as browser-click or browser-screenshot. There is no mention of prerequisites (e.g., the browser must be rented first) or exclusions.

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