Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

打开网页

browser_navigate

Opens an HTTP(S) URL in Chrome, reusing an existing tab for the same address or creating a new one without changing other tabs. Use it to visit web pages outside the IDE browser.

Instructions

用户要打开 Chrome 或访问网页时用这个,不要用 IDE 内置浏览器。打开一个 http(s) 地址。相同地址的标签已存在就切换过去,没有再新建,不改别的标签。

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

NameRequiredDescriptionDefault
urlYes要打开的 http 或 https 地址

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the non-obvious side effect: an existing tab with the same URL is reused, otherwise a new tab is created, and other tabs are untouched. It does not say whether navigation waits for page load, whether the window is focused, or what is returned, which leaves gaps for a browser-control tool.

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?

Three short sentences with the selection guidance front-loaded and the behavior rule after it; nothing is padded. There is mild redundancy between "打开 Chrome 或访问网页" and "打开一个 http(s) 地址", but it costs little.

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?

For a one-parameter navigation tool with no annotations and no output schema, the description covers the trigger, the resource, and the tab-reuse behavior sufficiently to call it correctly. Remaining unknowns (load waiting, return value, focus behavior) are minor for this complexity level.

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?

There is only one parameter and schema coverage is 100%, so the schema already documents the url field. The description's phrasing adds nothing beyond the schema, which is the expected baseline for a single fully documented parameter.

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 names a specific verb and resource ("打开一个 http(s) 地址"), so the agent immediately knows this is the page-opening entry point. It also contrasts with the IDE built-in browser, though it does not distinguish itself from sibling tools such as browser_tabs, which an agent might confuse with it when a tab already exists.

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

Usage Guidelines4/5

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

It gives an explicit trigger ("用户要打开 Chrome 或访问网页时用这个") plus a clear exclusion ("不要用 IDE 内置浏览器"). It stops short of telling the agent when to prefer browser_tabs or browser_go_back over re-navigating, so some routing ambiguity remains.

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