Skip to main content
Glama
Sign In
mcp-chromium-cdp

mcp-chromium-cdp

by duquesnay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

chrome_navigate

Navigate to a specified URL in Chrome, enabling page loads for automation, testing, and data extraction.

Instructions

Navigate to a specific URL in Chrome

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the action without revealing whether it waits for page load, replaces the current tab, or any side effects. The description adds no behavioral context beyond the tool name, which is insufficient.

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, 'Navigate to a specific URL in Chrome', with no unnecessary words. It is front-loaded and directly states the purpose.

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?

The tool is simple with one parameter, but the description omits important context such as whether it navigates the current tab or opens a new one, and does not differentiate it from sibling navigation tools. The lack of an output schema or annotations leaves gaps in understanding the tool's behavior.

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?

Schema coverage is 100% with the single parameter 'url' having a description already. The tool description adds no further meaning about the parameter, so the baseline score of 3 is appropriate.

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 the tool's action: navigate to a specific URL in Chrome. It uses a specific verb and resource, but does not differentiate from sibling navigation tools like chrome_open_new_tab or chrome_go_forward, so it loses a point.

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 when the user needs to go to a URL, but provides no explicit guidance on when to use this tool versus alternatives like opening a new tab or using back/forward navigation. The lack of exclusions or alternative mentions keeps it at an implied level.

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

Deploy Server

Other Tools