Nik-Browser MCP

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/19 tools missing one or more hints — browser_install_runtime (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); browser_launch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); browser_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — browser_install_runtime deletes at line 231 (archive.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — github_cli_status (line 509: result = subprocess.run([str(gh), "auth", "status"], text=True, encoding="utf-8", errors="replace", )

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool test coverage

Only 0/19 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Tool description accuracy

github_cli_status: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.