fix: ensure browser_snapshot correctly handles undefined arguments

[LymanBE]

This commit resolves an issue where mcp7_browser_snapshot would fail
with an "invalid_type" error if called with no arguments. The root cause
was 'undefined' being passed to Zod's parse method for a schema
expecting an object. The fix ensures an empty object {} is provided
if parameters are undefined.

Additionally, the npm build script in package.json has been updated
from 'tsc' to 'npx tsc' to improve build reliability, particularly in
environments where TypeScript might not be globally installed or in the PATH.

[LymanBE]

@microsoft-github-policy-service agree

[mxschmitt]

Suggested change

	"build": "npx tsc",
	"build": "tsc",

I don't think thats right, if you run npm install it will put tsc into the node_modules directory and add it to PATH as soon as you run a package.json script.

[LymanBE]

You're Probably right.

The main issue I found was the inability to handle empty args for the snapshot.

That seemed to break this MCP server for both Cursor and Windsurf at least in each environment I tested.

This seems like a large proportion of potential users for this, so rather than just complain with an issue report, I figured I'd share the fix I implemented and have found to work.

The other change wasn't necessary and I shouldn't have included it, so that's on me.

Let me know if you'd like me to adjust do anything to address this.

This MCP server is fantastic, btw.

[pavelfeldman]

Thank you for your PR, I updated our tests to account for empty arguments and fixed the issue, v0.0.24 should have it addressed.