豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content

Commit 57e7d51

Browse files
authored
docs(troubleshooting): add symptom for missing tools due to read-only mode (#1148)
1 parent 5dc00b3 commit 57e7d51

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

skills/troubleshooting/SKILL.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,12 @@ If the server starts successfully but `list_pages` returns an empty list or crea
4141
- **Check for flag typos:** For example, `--autoBronnect` instead of `--autoConnect`.
4242
- **Verify the configuration:** Ensure the arguments match the expected flags exactly.
4343

44+
#### Symptom: Missing Tools / Only 9 tools available
45+
46+
If the server starts successfully but only a limited subset of tools (like `list_pages`, `get_console_message`, `lighthouse_audit`, `take_memory_snapshot`) are available, this is likely because the MCP client is enforcing a **read-only mode**.
47+
48+
All tools in `chrome-devtools-mcp` are annotated with `readOnlyHint: true` (for safe, non-modifying tools) or `readOnlyHint: false` (for tools that modify browser state, like `emulate`, `click`, `navigate_page`). To access the full suite of tools, the user must disable read-only mode in their MCP client (e.g., by exiting "Plan Mode" in Gemini CLI or adjusting their client's tool safety settings).
49+
4450
#### Other Common Errors
4551

4652
Identify other error messages from the failed tool call or the MCP initialization logs:

0 commit comments

Comments
 (0)